facts to date (many of them obvious):
- we won't sacrifice the code base's integrity in the process
- we're hoping for more contributors by reaching out to new pools of people
- we're hoping to take the issues of open interoperability to the people and hopefully open up groupware, office document formats, etc a bit more
- if we do get an influx of developers who really know little to nothing about our culture and community, how do we effectively triage them into the project? or do we just try and keep them developing applications and separated from the project?
- if we do get an influx of users, how do we deal with them and what influence are we willing to let them have over our priorities?
- what are the marketing positions we will take?
- what level of quality and what breadth of features will we commit to on these other platforms?
- given that market share equals market clout, how do we avoid giving microsoft yet more leverage in industry by helping keep people on their platform as they continue to engage in their efforts against free software (think: hardware vendor relations (and not just kernel drivers), file format hijinks, single-platform / lock-in developer strategies)?
i think each of the above is solvable. i also think that we need to have answers put into words for the above so we can both work together and know we actually have answers rather than trusting quietly that we do even if we don't.
reasons the open issues are worth discussing
- these are big opportunities that come with reasonable but significant risks ..
- we need to have a coordinated idea of where the heck we're going with all these new platforms so we can get the most out of them and not (even unintentionally) work against ourselves
- our project dynamics (community, culture, etc) are valuable and worth ensuring the longevity of
reasons i'm not suggesting too many answers up front but instead asking all sorts of questions and generally poking people think:
- i probably don't have all the answers (no suprise to anyone, i'm sure ;)
- i'm not involved with the windows and mac ports and so don't feel like i am the best one to make up these answers, even if i am directly affected by these answers
- we need consensus.
- it'll be difficult to coordinate our efforts if the people involved with windows/mac ports are not in the game, too
- when i'm not poking and prodding the conversation doesn't seem to happen. i don't like that, but that's the way it is.
i don't think this needs to happen on blogs, either, but we lack a mailing list for this topic and even the planned win32 developers sprint won't bring together all the people necessary for this conversation (it will lack many from the other platforms). so i'm at a loss as to where this conversation will reach the audience necessary and not be off-topic.