Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Team System aka Team Block idea

<< < (5/7) > >>

Game_Ender:
Again, what are really going to have here?  Issue tracking integration with Code::Blocks, team management with Code::Blocks, source control integration with Code::Blocks, or a generic implementation of all three? 

The OP has seem to have left the thread without a super clear layout of what he wanted to accomplish, we could argue the best ways to do issue tracking integration all day.

MariuszP:
Game_Ender: I suggest You read the thread from beginning. This is supposed to be called Team Block - not bug block, bug related isuess are only one part of the whole system. I mentioned a lot of features, and I guess a lot of them will appear during the development. I'm not trying to create extra super detailed specification as this is one person project, and it is also supposed to be community driven so in the end it will be adjusted few times during development. It is quite normal for community projects.

Actually idea of Team Block came to me after taking a deeper look at Microsoft Team System. They are quite proud of their team system. So why we shouldn't be proud of our too? :D

Ideal solution would also bring support for continuous build, automated testing framework and many more. But i prefer to start from something simpler. Lets build small firework and then we move to building the space rocket ;)

Takeshi: I will think about reusing existing trac db structure. And hey - that is just great that TortoiseSVN now support bug-id string. I will download new version right now :D

David Perfors:
This is a very nice idea, but I think it is better to make sepperate plugins for every functionality, so every one can choose which plugin it wants (some don't want bug tracking, other don't want to have svn support)
An other advantage of multiple plugins is that it is easier to maintain.
Just my 2 cents ;) (I am looking forward to a first release)

takeshimiya:

--- Quote from: mispunt on August 29, 2006, 09:38:41 am ---This is a very nice idea, but I think it is better to make sepperate plugins for every functionality, so every one can choose which plugin it wants
--- End quote ---
But there should be some kind of TeamBlocks SDK (it may be not trivial to make) for communicating eg. between SVN <-> bugtracking.
On the other (more easier) hand you could have the same functionality but toggleable at runtime.

AFAIK when going for the Trac DB route, it would be rather difficult not having everything in the same plugin because the issue tickets, revisions, wiki articles and everything is tightly integrated and kept in the same SQlite DB.

MariuszP:
Eventually it will be set of separate plugins. But I don't plan to put bug tracking in one and change management in another. But for example svn will be separate plugin - that's for sure ;). Maybe I will even be able to reuse existing ones (as far as I know there is one).
If everything goes well then TM will be center for much more plugins. As I wrote - continuous builds and automated testing are just the few ideas that would be most helpfull.

mispunt: On more thing  - I plan to add some customization element. This is normal thing that every project in every company looks a little bit different. Some companies do not allow req changes during dev, other do, some handle bugs in one way, others do this in completely different way. So I plan to allow user to customize his view - does he need change management, should all the bugs be approved by somebody or maybe thay are moved to developer right after their appear in the system. There is so many combinations. And I plan to create TB as flexible as I can.

Takeshi: SDK. Well. Who knows. I think you are right. But i will think about this later.

Navigation

[0] Message Index

[#] Next page

[*] Previous page