On Wed. and Thurs. of this week I attended MIOSS, a workshop on
open-source software for molecular informatics. I'm sure there will be
a number of blog posts coming about this interesting event, but the
only one I've seen so far is from Rajarshi:
http://blog.rguha.net/?p=946

One of the topics floating around the discussions throughout was how
to encourage more community involvement/contribution in open-source
projects. On the way back to Basel I ran across this blog post
focusing on the same point, but directed at the python community:
http://jessenoller.com/2011/05/05/on-contribution/

I've started putting together a list of things people can do to help
with the RDKit. I've tried to roughly sort in order of increasing
difficulty/time required. I will eventually put this on the web page,
but I'd like to see if anyone in this group has any feedback or
additions first.

- Post to the mailing list and tell others what you are doing with the RDKit
- Make good bug reports
- Make detailed feature requests
- Answer questions on the mailing list
- Write todos, tutorials, or sample scripts
- Add/Expand/Improve the documentation.
- Add test cases for existing code
- Contribute a new descriptor (in python, java, or C++)
- Contribute a new fingerprint (in python, java, or C++)
- Contribute a new algorithm (in python, java, or C++)
- Contribute a reader/writer for a new molecular file format (probably
needs to be in C++)
- Fix a bug

Any other ideas or feedback?

Anything I can do to make some of these easier?

-greg

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Rdkit-discuss mailing list
Rdkit-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rdkit-discuss

Reply via email to