Before I go too much further, do you guys want these feature requests in the *jsource* repo, or should we make a new repo?
An alternative is to have a separate github project specifically for proposals that may or may not be implemented, while they are under discussion. Here's how python does it: https://github.com/python/peps At the company I work, we also do something like this... We have a separate "requests" JIRA board where anybody can submit anything for discussion, and then a weekly triage meeting where we decide what to do with the requests... If we decide to implement it, we move it to the "actual work to do" project... Sometimes this involves quite a bit of rewriting / clarifying / breaking or joining of tickets / etc. If we think we might want a separate repo down the line, we should probably act now. With a separate repo you could also give a person (like me) doing this request management stuff access to that repo, for tagging and organizing tickets, without necessarily giving them write access to the code. (maybe you can do this anyway with github's admin tools?). A separate repo would also allow us to give users a single point of contact, without worrying about which repo (qtide, base9, etc) they should post it to. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
