I also like the developer wiki idea. Risk: keeping a wiki accurate for an evolving system requires an investment of time...

On 4/8/19 11:00 AM, Norman Feske wrote:

Everyone,

• Can you think of concrete examples that you'd find helpful?

• Which areas of Genode do you find most challenging?

• What are the topics and application domains you'd enjoy reading about most?

One of the trickiest areas for me has been mixing the Libc environment with Genode native facilities (rpc, events, shared memory) in the same component.

Articles on networking would also be helpful. E.g., which of the common socket timeout techniques will work as they do in Linux? A list of known differences along these lines could be a great time saver.

// Steve Harp

Hi Steve,

El 8/4/19 a las 18:36, Steven Harp escribió:

I also like the developer wiki idea. Risk: keeping a wiki accurate for an evolving system requires an investment of time...

I find it useful that, for instance, the online documentation of Ubuntu normally tells you for wich versions of the system the article content has been approved. In the Genode Wiki, the author of an article could add the version he was using and other user can later add versions for which they could apply the article successfully. As soon as information in the article gets outdated, the affected parts could get split up by another user with the newer version like this:

Step 1 ====== ... Step 2 ====== :For version X and Y: ... :For version Z: ... Step 3 ====== ...

When an article becomes too complicated to read because of this, it can be split up completely into distinct articles about the same topic - for instance, one named "Topic A, versions up to Y" and one named "Topic A, versions beginning with Z". They would still contain the "approved version" tags but one can easily decide which articles to skip just by reading the title.

Articles on networking would also be helpful. E.g., which of the common socket timeout techniques will work as they do in Linux? A list of known differences along these lines could be a great time saver.

I could add information about the native Networking components of Genode but am not much into stuff like sockets and ported stacks ontop of that.

Cheers, Martin

On 4/1/19 2:58 PM, Valery V. Sedletski via users wrote:

On 31.03.2019 23:33, John J. Karcher wrote:

...

Hello Genodians,

The content on Genodians.org has been so interesting and varied that I worry we might lose valuable content in the sheer volume as time goes by.  Here are a couple of ideas that I thought might help (probably already on the "to do" list, but just in case):

1. "Sticky" / "Featured" Posts - Things like the announcement for the

latest release, other important news, etc. should probably be kept at/near the top or in a special area.

2. Search / Filter Tags - I think it would be helpful to add "tags" to

the posts to make it easier to find items on a certain subject.  I would recommend defining the format and adding the tag data as soon as possible, even if the feature isn't implemented for a while - it's always harder to go back over a lot of data than to enter it as the records are added.

Just food for thought...

Thanks!

Yes, I agree that these features are good to have as they would make Genodians.org much more convenient to use. But this will require some scripting to implement these features. Currently, Genodians.org is implemented as a simple web site with static content, only.

Indeed. The "featured post" feature is the easier of the two, and shouldn't be too hard to implement with the current system.

I only brought up the "tags" idea at this time, because it will be a lot of (thankless) work to go back and add tags later. The data format could be defined (and data entered) before the feature is actually implemented.

Like I said, just a thought.

Thanks!

John J. Karcher devuser@alternateapproach.com

Hi Stefan,

I can understand the wish for a more structured approach, but I have an odd feeling about the "sticky/featured" way. The question is: who decides what post becomes a featured one? I have understood genodians.org as a platform of community members with equal rights. In contrast to the "official" genode.org site, where already announcements, releases etc. can be found in the "news" area, and which is administrated by Genode Labs, genodians.org is a conglomerate of free developer content. Of course, Genode Labs as domain holder keeps the right to add/remove developer repositories, but apart from that everyone is equal member of the platform, and the last post is presented first. Moreover, interests are different regarding the visitors of the webpage. Newcomers will have different interests than more experienced users. Therefore, me personally would not like that "featured" feature.

thanks for sharing your opinion. I agree 100%. Sticky posts call for policy. But by design, the site tries to be as free from policy as possible.

I recognize John's point that he regards some articles as a kind of mileposts for orientation. In my opinion, however, the best way to keep important posts in the collective memory is to cross-reference them from newer posts. This way, readers may click through related articles and eventually discover the most relevant ones.

The search and filter option is clearly a good convenience feature. As Valery has already mentioned, by now it is statically assembled content. So a first approach might be to find a way how Gosh can easily differentiate "tags" without disturbing normal content production much. Then tags could be filtered out when creating html out of a post. The script for producing the pages could collect the "tags" and produce one page per tag under genodians.org/tags/... where all articles are referenced inside. At the end of an article the tags of that one would reference the related tags pages.

What do you think about that approach? Would it fit your needs? Does anybody would like to step in here?

The tags can be implemented like you suggest (the last part about the cross-referencing is a bit tricky though).

Regarding a suitable GOSH markup, the pipe character at the beginning of the line comes in mind. In GOSH, this is the markup for annotations.

| Annotations are useful in drafts of big documents | to highlight open questions or parts that are work | in progress. But in relatively short blog postings, | they have no use.

Since tags are actually kind of an annotation, we could specify tags as a space-separate list of words like this (e.g., at the end of the article, like a footer):

| storage performance cryptography

With this scheme, each tag can only be one word. But I think that's fine.

The list of tags could go into a dedicated box just below the list of authors at the left side of the page.

That said, I'm not too eager to implement the feature immediately. ;-)

Cheers Norman

On Tue, Apr 02, 2019 at 12:23:21PM +0200, Martin Stein wrote:

I think that at least an agreement on how to define tags would be sensible. So, authors can start adding them while the effort of examining them may be delayed.

El 2/4/19 a las 10:04, Norman Feske escribió:

...

Since tags are actually kind of an annotation, we could specify tags as a space-separate list of words like this (e.g., at the end of the article, like a footer):

| storage performance cryptography

With this scheme, each tag can only be one word. But I think that's fine.

What about this approach:

| tags: "storage" "performance" "symmetric cryptography"

It would distinguish a tags annotation clearly from any normal annotation and allow for multiple words in a tag.

I've opened up an issue at:

https://github.com/genodelabs/genodians.org/issues/11

so we can discuss the technical details there.

Regards Stefan

Cheers, Martin

---

Genode users mailing list users@lists.genode.org https://lists.genode.org/listinfo/users