|Re: [p2-dev] 3.8 / Juno wishlist|
@ DJ: Thank you for the “equinox.p2-inbox” hint, it was very useful.
I’d like to participate in the project activities, I just don’t know how they are organized or how I could help. I would appreciate any suggestions you might have.
In my opinion, working on random fixes and docs could be tricky for someone who is not really familiar with the project. As mentioned during the p2 call, sometimes there is no documentation - I think that, no matter how well the code is written,
assumptions made using the code exclusively (without knowledge of the concept behind it and existing use cases) could often turn out wrong.
I understand that it would be nice if participants could progress by themselves but working on a topic of one’s own liking may often turn into fruitless discussion, if it doesn’t fit the project vision. That’s why I asked about priorities on the call –
having a community guy interested in getting something done in a reasonable time frame (e.g. 1 release) could smooth out the process a lot.
This kind of support would bring the focus that most of beginners don’t have and would ensure that the requirements and scope are clear. It would also build confidence in understanding p2 concepts and would naturally result in helping other people.
To build on that particular point about bugzilla. To stay on top and involved, we recommend people to follow the equinox.p2-inbox user in bugzilla (log into Bugzilla, then edit your mail preferences to watch the equinox.p2-inbox@xxxxxxxxxxx user). This allows you to keep an eye on things get a feeling for the types of bugs which are coming in and help determine what users feel the hot issues are.