Hi Carsten Regarding documentation:
A simple idea on how to mark the quality of single documentation pages could be to include the date when the page was last updated (or checked, if no updates were necessary) in a prominent place (e.g. below the title) on the page. This information allows to get a confidence level for a documentation page more quickly and I believe it would also increase the confidence to report if it is out of date. We had the inverse, where pages were explicitly marked outdated. But that can be forgotten as well. So informing when the page was up-to-date the last time should add value and is cheap to implement. Regards Julian On Mon, Sep 19, 2011 at 6:59 PM, Carsten Ziegeler <[email protected]> wrote: > Hi, > > last week saw the first Apache Sling community event, the adaptTo in > Berlin. This was a great event, nicely organizied by pro!vision. > Thanks go to pro!vision, especially to Dominik, for organizing and > sponsoring this and thanks go to Adobe, especially Gabriel for > sponsoring and supporting this event. But as important a big thanks > goes to all the speakers and each and every attendee! I was great > meeting you! > > The first day was a real community day focused on Apache Sling and > related technologies. I was very happy that many of the attendees were > using Sling in own solutions and projects, though people using Sling > with the Adobe offerings made up the majority. But the important thing > to notice is, that we have a real community behind Sling which is more > than just one company. And that's great - so we're on the right track > as an open source project! I would love to see more from the whole > community but I guess this will happen over time. And maybe this first > get together is the starter for even more to come. > You'll find all the slides at [1] and some photos at [2]. > > There were many great talks and it would be unfair to just mention one > or two of them. But :) I would like to highlight my "The Future of > Apache Sling" talk, just because I think the future is always > important. As mentioned in the talk, these slides represent my > personal vision, so it might or might not happen. It is up to us here, > the community, to define the future of Apache Sling! > There are several areas were Sling could improve, but one in > particular is documentation. Without wanting to repeat all the lame > excuses from the panel we had, I really would like to ask for help > from the community. Finding bugs or problems and reporting them, is > one of the first steps in becoming part of an open source community. > Now, finding these things in code is one thing, but finding them in > the documentation, especially in tutorials is another of those > important things. Or reporting missing or unclear documentation. If we > know where and maybe how to improve or correct the documentation this > will be a real improvement everyone would benefit from. And if you > want to write some docs, tutorials, or about your experience with > Apache Sling, just send these things, and we'll be happy to add them > to our docs. And all these are the first steps in becoming an Apache > Sling committer! Being a committer is in no way tied to writing code, > providing documentation is another way of being involved. > > We'll discuss other new tasks or features for Apache Sling in separate > tasks, and I'm happy that Markus already started such a thread. Really > appreciated! > > And finally, this was the first get together but it was definitely not > the last one! Everyone I spoke with was very enthousiastic about > repeating this. There are no concrete plans yet but several different > ideas. So I hope to have a next edition sometime in spring next year. > And hopefully we can add a hackathon day were we can sit together and > hack some cool things for Sling :) > > > [1] http://www.pro-vision.de/adaptto > [2] http://www.flickr.com/photos/gabrielwalt/sets/72157627675031546/ > > Regards > Carsten > -- > Carsten Ziegeler > [email protected] >
