Thread: RE: [Gamedevlists-brew] Gauging the vibe...
Brought to you by:
vexxed72
Menu
▾
▴
gamedevlists-brew
|
From: Paul Z. <pa...@bl...> - 2004-12-10 21:03:03
|
I agree with Matt-- I think its best to choose who to add to the pool, rather than constantly dredging it clean. -Paul AKA Keless -----Original Message----- From: gam...@li... [mailto:gam...@li...] On Behalf Of Matt Sponer Sent: Friday, December 10, 2004 12:46 PM To: gam...@li... Subject: RE: [Gamedevlists-brew] Gauging the vibe... Guido, If this list is too open then it is not differentiated from the BREW Forums. I also believe that it's easier, more polite, and less maintenance to only allow people you invite instead of allowing everyone and then removing them-- the gatekeeper role is probably more enjoyable than a policeman role, since you would only need to make a join/no-join decision once instead of feeling you must read most of the list traffic and constantly judge if someone is generating too much noise.=20 Matt. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.=20 http://productguide.itmanagersjournal.com/ _______________________________________________ Gamedevlists-brew mailing list Gam...@li... https://lists.sourceforge.net/lists/listinfo/gamedevlists-brew |
|
From: Tom P. <bre...@ac...> - 2004-12-11 03:16:49
|
FWIW, there are already a few invite-only, closed lists. Chris Hecker started one. George Broussard started another. Not only to keep out newbies & trolls and unproductive flaming and oneupsmanship, but also in an industry where there's so much proprietary information, it is a way for indies to share info freely without worry. I've heard of private file-sharing groups where the members want to protect the network against attack by outsiders (e.g. RIAA). They use a "sponsor" model where every new invitee is sponsored by a member. If an invitee is banned from the network, then the sponsor is also expelled, in order to provide strong incentive -- not only on the sponsor's part, but the invitee also is liable for his sponsor. Obviously, we don't want or need such strong protection of the list against newbies (although you can look at the BREW forums as having been attacked by newbies, eh). I just bring it up to put the openness of this list in perspective. This list is not so closed. E.g. I was invited to Broussard's Game Illuminati list by a friend, and Broussard nixed the invite, saying that mobile game developers were not hardcore enough for that group. Members of that list are not even supposed to acknowledge its existence, i.e. 1st rule of fight club. --t |
|
From: Guido H. <gh...@g3...> - 2004-12-11 03:37:26
|
Yes, I am familiar with these lists and some of us are actually members of some of these lists as well. In actuality, I would like to make this list completely private and allow new subscribers by invitation only but it seems that the sourceforge list setup that we have here doesn't allow for tha - at least not that Tom Hubina or I are aware of. Otherwise I'd be all for closing off the list to outsiders so that we can also discuss proprietary and sensitive matters here. Guido |
|
From: Tom H. <to...@am...> - 2004-12-11 03:52:25
|
The privacy stuff is limited because it is on SourceForge and, well, they're all about "open" .. heh. I was under the impression that this was going to be a technical list, but I'm curious, what kind of proprietary and sensitive matters would folks be willing to discuss on a private list? I'm on some myself already and while they start off strong it seems like the sensitive stuff ends up getting discussed in private messages anyway ;) Beyond that, if there's people we trust enough to discuss sensitive stuff with, what's wrong with inviting them on to the private lists already in existence? As Guido mentioned, we're already on them so in theory we can do that if we want. For me personally, I like having a focused technical list that can be a better resource than the BREW forums and I'm happy to keep the secret stuff in IM or private emails. I was half tempted to suggest that this list be opened up to J2ME as well as BREW, but that can always be a different list. Tom > -----Original Message----- > From: gam...@li... > [mailto:gam...@li...]On Behalf Of Guido > Henkel > Sent: Friday, December 10, 2004 7:37 PM > To: gam...@li... > Subject: Re: [Gamedevlists-brew] Gauging the vibe... > > > Yes, I am familiar with these lists and some of us are actually > members of > some of these lists as well. In actuality, I would like to make this list > completely private and allow new subscribers by invitation only > but it seems > that the sourceforge list setup that we have here doesn't allow > for tha - at > least not that Tom Hubina or I are aware of. Otherwise I'd be all for > closing off the list to outsiders so that we can also discuss proprietary > and sensitive matters here. > > Guido > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Gamedevlists-brew mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-brew > |
|
From: Tom P. <bre...@ac...> - 2004-12-11 04:16:28
|
> what kind of proprietary and sensitive matters would folks be > willing to discuss on a private list? One example: while particular device specs are discussed on the forum, there is no easy-to-query database that covers all the devices because Qualcomm isn't allowed to publish it. We could. It's simple enough to write and share a device profiler-benchmark applet. We could share the output. It would make our lives easier. It would give competitive advantage to the recipients. If you are not self-employed, would your employer allow you to share such data? Well, I doubt mine would, if it were entirely my own effort. However, as a collaborative effort, who would own such data? While the relative sales numbers for various handsets are pretty obvious, that's another sensitive area where people might share data. > For me personally, I like having a focused technical list that can be a > better resource than the BREW forums and I'm happy to keep the secret stuff > in IM or private emails. Part of the value in the list is that you get contribution from several people, not just a couple guys. >I was half tempted to suggest that this list be > opened up to J2ME as well as BREW, but that can always be a different list. Yeah, I was going to suggest the same thing, seeing how we all probably are doing J2ME work as well, and probably other wireless mobile APIs like Symbian and Smartphone. The occassional off-topic email probably won't hurt, especially if you're talking about porting btwn platforms. --t |
|
From: Aaron I. <ais...@ap...> - 2004-12-11 04:17:56
|
RE private lists: There are some technical things that I've discovered over the past 2 years developing for BREW that I'd be happy to share with people that I knew would return the favor and share what they know. This detailed knowledge is what makes us valuable developers. Sharing that knowledge with our peers make us even better. However, giving away that advice for free to people who will only use it to compete with us and not expand what we are capable of, might not make sense. The biggest downside to having a secret list is that some very knowledgeable, but not well connected, people could be left out. RE J2ME: I would not mind if this list also focused on J2ME, unless the traffic and volume got too high. I have started porting our apps to J2ME, and I already have several questions that I couldn't find answers to. If not this list, then I would love to be part of a similar list focused on J2ME. -Aaron > -----Original Message----- > From: gam...@li... > [mailto:gam...@li...] On > Behalf Of Tom Hubina > Sent: Friday, December 10, 2004 10:52 PM > To: gam...@li... > Subject: RE: [Gamedevlists-brew] Gauging the vibe... > > The privacy stuff is limited because it is on SourceForge > and, well, they're all about "open" .. heh. > > I was under the impression that this was going to be a > technical list, but I'm curious, what kind of proprietary and > sensitive matters would folks be willing to discuss on a > private list? I'm on some myself already and while they start > off strong it seems like the sensitive stuff ends up getting > discussed in private messages anyway ;) > > Beyond that, if there's people we trust enough to discuss > sensitive stuff with, what's wrong with inviting them on to > the private lists already in existence? As Guido mentioned, > we're already on them so in theory we can do that if we want. > > For me personally, I like having a focused technical list > that can be a better resource than the BREW forums and I'm > happy to keep the secret stuff in IM or private emails. I was > half tempted to suggest that this list be opened up to J2ME > as well as BREW, but that can always be a different list. > > Tom > > > -----Original Message----- > > From: gam...@li... > > [mailto:gam...@li...]On Behalf Of > > Guido Henkel > > Sent: Friday, December 10, 2004 7:37 PM > > To: gam...@li... > > Subject: Re: [Gamedevlists-brew] Gauging the vibe... > > > > > > Yes, I am familiar with these lists and some of us are actually > > members of some of these lists as well. In actuality, I > would like to > > make this list completely private and allow new subscribers by > > invitation only but it seems that the sourceforge list > setup that we > > have here doesn't allow for tha - at least not that Tom Hubina or I > > are aware of. Otherwise I'd be all for closing off the list to > > outsiders so that we can also discuss proprietary and sensitive > > matters here. > > > > Guido > > > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide Read honest > & candid > > reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start > reading now. > > http://productguide.itmanagersjournal.com/ > > _______________________________________________ > > Gamedevlists-brew mailing list > > Gam...@li... > > https://lists.sourceforge.net/lists/listinfo/gamedevlists-brew > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide Read honest & > candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Gamedevlists-brew mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gamedevlists-brew > |
|
From: John S. <jo...@se...> - 2004-12-11 09:16:44
|
> RE private lists: There are some technical things that I've discovered over > the past 2 years developing for BREW that I'd be happy to share with people > that I knew would return the favor and share what they know. This detailed > knowledge is what makes us valuable developers. Sharing that knowledge with > our peers make us even better. However, giving away that advice for free to > people who will only use it to compete with us and not expand what we are > capable of, might not make sense. Agreed. Plus I like super sekret clubs. > RE J2ME: I would not mind if this list also focused on J2ME, unless the > traffic and volume got too high. I have started porting our apps to J2ME, > and I already have several questions that I couldn't find answers to. If > not this list, then I would love to be part of a similar list focused on > J2ME. What he said. How about that j2me, eh? |
|
From: Guido H. <gh...@g3...> - 2004-12-11 17:42:43
|
> How about that j2me, eh? Alright, sure, let's open this mailing list to J2ME or other mobile development related discussions as well. As Tom said, most of us are probably dabbling in these different areas as well anyway so we can just as well talk about it. Guido |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X