(08-26-2009, 03:38 PM)Wesley link Wrote: When working in a team communication is very important.
(08-26-2009, 03:38 PM)Wesley link Wrote: We no longer want to use Mantis, but use Trac instead.
Sorry but that made me laugh. Your saying that communication is important - and yet your going ahead and changing the way we do tickets without "communicating" with us first and asking how we feel about using trac. Mantis isn't that bad - at first me and tomozj both wanted to use trac, but Badeend inisted that we must use Mantis, which I was pissed off about for days, because at the time it was my project and I was being forced into using mantis. I felt like quitting.
But now my attitude has changed. I prefer mantis - It has features similar as trac, so I don't see why we can't use that. It also has a better priority system and we can assign our tickets to a different status - e.g, if we require feedback, if a bug has been acknowledged or confirmed, etc. It is a lot easier to use to.
The only advantage is the wiki, but we could use a MediaWiki somewhere. Tortoise svn can be used for the source management.
Perhaps discussing changes before making them is one of the ways you could improve communication. But I'm not blaming you for that. As far as I know it was Peter who insisted the change to trac without discussing it first, and yet it's ironic how he has the right to criticise.
(08-26-2009, 03:38 PM)Wesley link Wrote: We'd also like there to be more discussion before changing important things or adding features. Ask other developers in the #lvp.dev IRC channel, post here on the forusm or have them comment on the ticket at Trac.
Sorry but that isn't going to work. Do you not think I haven't tried that? In the past I have constanty asked other developers about features in IRC, added numerous notes to tickets on the mantis, and made topics in these forums - but people rarely paid attention or acknowledged this. The only person that I used to have a good full on discussion about features with was tomozj. When I get into something, I'm a really active developer. I like to develop things without having to wait till the next day or week until someone is active.
We're currently a team of four people remember. Sure there are other developers like [Griffin]* Felle and Pugwipe, but they aren't very active and haven't done much for LVP.
* Although I must say [Griffin] has made a few commits lately and has indicated he is working on an anticheat
(08-26-2009, 08:10 PM)Wesley link Wrote: Another suggestion I have is to start adding a small description to the header that each file has in the new PreCompiler branch.
We do that already though. (Well, I do anyway
)Some changes need to be made the way I see it. Firstly I would like to see the dev channel only open to developers and head management and feature's strictly decided by developers to. Fair enough it's okay making a suggestion, but people shouldn't be able to make feature tickets and expect us to do it*.
Secondly I would like some changes to the way people report tickets to. Only developers should decide and write feature tickets, anyone else should just do bug reports.
Thirdly I think developers should assign their own tickets to themselves. If a developer writes a ticket, they should do it, and not expect others to do it.
Finally I'd like a proper beta team. Not the whole crew as beta testers like it was insisted upon last time (yeah, when it was my project and I was forced into decisions again) but instead people from the community. Currently there are about 30 people in .beta. The only good beta testers have been Chillosophy, Joe, estroe, Pugwipe, Twilight and Maka.
* That ticket was only an example of what I presume was made without any discussion within the development team. I'm not certain on this because it was made at a time when I was not a developer.
P.S I don't mean to be disrespectful in the slightest, just incase anyone takes this the wrong way. I do understand that developing is a voluntary position and people can't always guarantee work.