Should we start a WikiTree Enhancements Project?

Question

 

 

I'm thinking a project might be a way to bring together those who are interested in helping work out new features and improvements.

 

Related question: Would this be merged with the WikiTree Tools project? That's intended to be a group for those developing external tools and add-ons, like Roland is doing.

 

A separation of internal and external tools might make sense, but there might be a lot of overlap between the topics/tools being discussed, and it might be the same people. If it's going to be the same people and the subject material intertwines, two projects just adds complication, right?

 

Thoughts?

Answer 1

I think a common project is a good idea for the reasons you mentioned, but also because I can imagine a popular feature in an external tool getting implemented in the site, or a suggested improvement to the site that might not be feasable getting implemented as an external tool.

Answer 2

One is fine, but I like it!!

Answer 3

I guess it depends on what you mean by a WikiTree Enhancements Project. Do you mean just people giving their suggestions for the site, or actually doing development?

If it's the latter, then I think keeping it together with WikiTree Tools makes the most sense, because it's going to be the same people.

If it's the former, then maybe separate makes more sense, but then I'm not sure a Project is the best format; that's pretty much what people already do here on G2G. :)

Unless, I suppose, you're thinking of people doing more than just suggesting things, and actually helping work out the details of changes to the site...

Comments

Hey Lianne. I'm not exactly sure how it would out in practice -- we'd have to experiment and find out -- but I do envision project participants who do more than just post suggestions. I'd like them to help think through the details and test new releases, if not actually code anything.