Am 04.09.13 11:06, schrieb Lukasz Lenart: > I have changed title to not interfere with the main topic Thanks! > 2013/9/4 Christian Grobmeier <[email protected]>: > >> We just need to know that potential Struts committers already have more >> barriers than the average GitHub user. At least when the ICLA is on file >> we need to make it as easy as possible to contribute. Compared to all >> other projects I know at the ASF I think its pretty difficult to >> contribute Struts > Could you elaborate a bit more? How can we improve that? > Sure. Hopefully others who are not familiar with the ASF in general will speak up to.
When I first looked at Struts, the website was a mess. It still is (but we're working on it). I was confused by countless topics. It is in my genes to look at the source code immediately, but the Struts sources were huge. Unfortunately i was not able to connect documentation to the source code. I started with the JSON plugin first and got this: http://struts.apache.org/release/2.3.x/struts2-plugins/struts2-json-plugin/index.html which is an empty page. I looked into the source code and was not quickly able to find out whats going on. Then I found some docs in the wiki. But the correlation of Struts documentation to the wiki and static webpages is black magic. Honestly, if I couldn't ask you (Lukasz) I would still not know how these things are all tied. And believe me, I am going to continue to ask you on it. This is a huge help for others: http://struts.apache.org/helping.html But I believe given our huge website its hard to find. It says how I create a patch and how join the mailing list. But thats not enough in the Struts case. I would love detailled, easy to understand instructions how a non-committer can fix typos on our docs in less then a minute. I mean instructions which you don't need to search. I think we'll need to explain how we are building things. I think we should make things like this page: https://cwiki.apache.org/confluence/display/WW/Struts+Next more prominent. We should also explain what we would do when we start working on v2.5 (do we create a branch? do we just commit to the trunk? and so on). When I go to Commons I don't have such problems. I check out a small component and send in a patch. If I am doing it wrong, somebody tells me. But in Struts land everything is so huge. For me it is all with a better documented workflow and better websites. Hopefully others, non-committers now put some ideas in here! Cheers Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
