...
Learn how to use an internet search engine. Try to find information before you ask. The results may be hard to understand or confusing and be careful about reading snippets without taking in some of the larger context. But then your question will be better defined. Bonus if you can quote a web page as part of your question.
| Wiki Markup |
|---|
Your mentors may get too busy to follow the details of activity in your podling. Use the \[MENTOR\] tag in the subject to try to catch their attention. Escalate to the Incubator IPMC if they still don't have time to respond. |
Your Rights
Some folks want there to be a "bill of rights", but you don't have any "rights" because there are no authority figures at Apache to enforce those rights. Any "violations" have to be dealt with "socially". You can seek help from the IPMC or even the board, but even they are volunteers and will try to address the problem socially as well.
...
- The primary goal is to cover your and Apache's butt legally. This may require you to change build scripts and release packages in a way that is painful for you and your customers. 2.
- Apache only officially releases source code. This may be a pain point for any existing customers used to downloading binary packages.
- 3. At Apache, open source isn't just about making released source code available. It is about trying to get the community involved early and often before the source code is "release-ready".
While the first two are very important from a legal perspective and are a blocker to graduation you'll find that ultimately 3 is the important blocker. Yes you must get your legal ducks in a row but if your podling can not generate a sufficiently large self-sustaining community then it is not going to succeed as an Apache project.