Do we want the Developers category not to be visible to the public? I think
its valuable that the vassalengine-devel list has public archives. (Which is
part of why I’m still posting to it.)
On 12/13/07, uckelman messages@forums.vassalengine.org wrote:
I would agree with openness. It seems a bit cabalistic for an
open-source project to have the developer discussions private. At a
minimum, read access should probably be available. I would say
posting access should be fine too, unless people start posting
non-development related stuff. But I guess if that happens with the
forum, you can just move it to a more appropriate category.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Thus spake “Tim Byrne”:
Right now, it’s possible for anyone to subscribe to the dev list, which
I think is fine. (I’ve subscribed to the dev lists of projects in the
past because I had a question that only the developers could answer
and I wanted to make sure they saw it. This seems an appropriate use
to me.) The need to subscribe is a sufficient barrier to make people
stop to consider whether what they want to post should go to the dev
list, but maybe it’s more than is necessary, even.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
It’s certainly something worth debating; And in an ideal world, I would agree. However, I expect the forum to get a heck of a lot of interest when it goes public.
The problem is there are a lot of wanna-be developers who will want a hand in every decision; And one of the facts of life is that decisions are going to be made which will make a small portion of people irate, and they are going to interfere with our discussions.
Our interest is in making Vassal best for everyone; That’s gonna annoy Star Wars Minis player Bob who just wants his flying beast in 3D, or else. In the past I agree that openness was the best policy, but I think that needs to change now that we will potentially have a much higher profile.
Joel is right, if you join the mailing list you’ll have access to the dev discussions whether you like it or not. It just means I need to make sure users on the email-list also have an account with permissions to “Developers” on the forum.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
I’ll also add that this discussion we’re having right now is a textbook example of why we need a private folder; If you ask an end-user if he should have access to everything, the answer will more often that not be “hell yeah!”, that’s useless information for us.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Let’s start with open unless a problem develops. Having the developer’s form be public is useful for people who are considering becoming contributors. I’d expect that the ability to read through dev chatter from the past would help draw new developers in.
rk
Post generated using Mail2Forum (mail2forum.com)
Thus spake Bsmith:
I don’t agree. The reason we’re having this discussion is because you made
the folder private.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Thus spake Joel Uckelman:
On reading what I wrote, I realize this sounds accusatory, which wasn’t
intended. I’m merely pointing out that we hadn’t had this discussion before
becase there’d been no occasion for it.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
You were being a smart-ass Joel! 