John Casey wrote on 10/8/18 1:33 PM: > Hi all, > > I've been working on a project for 4-5 years now which I think would make a > good Apache project, at least in terms of it being valuable, high-quality > software. We're using it internally for our production systems at work, but > the code is open (hosted on GitHub). Our process to date has been somewhat > lacking (starting out as a 1-man project, now up to 3-4 regular > contributors). The project is called Indy > (https://github.com/Commonjava/indy).
Where's CONTRIBUTING.md? -- - Shane ASF Member & Comdev PMC The Apache Software Foundation P.S. The above is both a snarky and a serious comment. The first step - besides coming here to ask, which is super-awesome!!! - is to make sure that the homepage for your project is *explicitly* welcoming of both new contributions and new committers. I.e. not only do you want to see people submit patches, you welcome people suggesting new directions or adding new modules, and would be happy to add them to your maintainers. Plus, as noted elsethread, ensure that all the rest of the bits of managing a project - issues, docs - are all at public URLs and have their own friendly "How to..." documentation right on the front page. ProTip: Just publish your docs now (unless they're seriously wrong because they're out of date). Perfection does not help community; pretty good stuff that needs some obvious fixes helps community. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
