James, yes absolutely. IMHO the best forum to initially float new ideas is the mailing lists since they are most open for discussion and seen by a bigger community. After things get a bit more concrete, I would capture the enhancement idea as clearly as possible on GIThub as an issue, so the coding-related folks can relate to it. Also, a reference to the created issue then can take the high-level discussion from the list to the concrete thread on GIThub, thus keeping the list threads to a reasonable level.
WDYT? Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Tue, Sep 6, 2011 at 8:37 PM, James Thornton <james.thorn...@gmail.com>wrote: > Hi Peter - > > For Neo4j-related ideas discussed here that are not bug fixes, do you > recommend that we move the discussion to the Neo4j mailing list before > posting them to the issue tracker? > > - James > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
