After 4 years, the new CodingTeam release is now published! CodingTeam 0.9.4 is together a bug fixes release and a major feature enhancements one as it introduces a bunch of great new features.
The 0.9.3 was published in june 2010. It's been 4 years and almost 200 commits (mostly made since october 2014) to create the new release. This release brings important new features like:
- Git support (basic functionalities only for the code browser)
- Teams support
- Lot of new statistics (on project activity and source code)
- Better roadmap (with statistics on distribution and progression of reports)
- Totally new look'n'feel, with a modern CSS/HTML5 template
We added a few little improvements too. A huge amount of bugs have been fixed and the Mercurial support is now better. We also added the ability for a user to be automatically warned about new elements in his dashboard. A few other changes have been made too:
- added preselected filters in the bug tracker
- compliance with the latest PHP5 evolutions
- removed all XMPP features related to chatrooms or presence
You can download CodingTeam 0.9.4 here. If you were using CodingTeam 0.9.3, you have to read and execute scripts/miscellaneous/upgrade093-094.php to update your database. You might also take a look at our documentation.
The CodingTeam website hosted at http://codingteam.org has just been updated.
The goal of this website is to present CodingTeam and to inform potential developers, users and administrators about this software. It provides a full description, an historical presentation, a features list, some screenshots and contact informations.
You'll see some screenshots and informations announcing brand new features that will be shipped in the next CodingTeam release. By the way, we can inform you all that CodingTeam 0.9.4 will be released before the end of the year.
Feel free to take a loot at our new website: codingteam.org!
For those who didn't notice, I'm glad to announce that the CodingTeam software forge project is now living again. Indeed, after 2 years of rest, a lot of work on CodingTeam have been done recently.
So, what's up with this project?
Our goal is to produce an up-to-date and enjoyable new version within this year. We added a few cool functionnalities to the trunk and we plan to add more before the release. We won't give you any time projection at the moment, but we hope to have a new release before 2015. So, stay tuned!
This is a very tiny news just to let you know that CodingTeam will be present at the RMLL (Rencontres Mondiales du Logiciel Libre).
If you want to talk about CodingTeam, software forges or programming, you may come to visit us on our little stand!
We will keep you informed of events of the week on the CodingTeam Blog.
Another CodingTeam meeting was organized in Paris. Last time we were only 5, and this time, we were 7. If you are living in Paris, watch the forum for a probable future meeting!
The appointment was in downtown Paris (Châtelet) at 6 PM and our meeting ended around midnight. We talked a lot about various subjects like:
- the daily server problems on codingteam.net and the recent call for contributions to rent a better server (the full call message can be read in french and english on the codingteam.net homepage ; and, by the way, we need your help!)
- the lack of importation mechanism in CodingTeam and the necessity to have a system that allow to save our data and to switch to another software forge without data loss
- the need to write an installation script for CodingTeam
- the futures plans for CodingTeam and the planned releases
- the progress of the correction of a few bugs
- the fact that parisian sell Breton galette under the ridiculous name of "salty crêpes"
- and so many other topics!
For your information, after the flammekueche of the first meeting, we chose pizzas this time.
Here are a few pictures of us:
So it was a very pleasant meeting between good, rich and sexy people (the next time we'll try to make better photos of us)! Hope to see you in the future!
It's now the time to publish the results of our survey. I want to thank you all for your participation, as we get nearly 80 answers to the "CodingTeam survey 2011".
Even so our survey suffered from a few weaknesses like the fact that a few questions not addressed to all of our users were mandatory, the result provide us a lot of useful informations. The problem with our mandatory questions (features scores) is that the scores are devalued and there were confusion in the responses.
So, let's start!
The CodingTeam software forge is a young project and it's used by young people! 57.89% of our users report being between 15 and 25 years. There are 38.16% of our users between 26 and 60 years. On the other side, there are fewer users that are more than 60 years (2.63%) or less than 15 years (1.32%). Thus, we can see that the majority of our users are young, with nearly 60 percent of them under 25.
In the beginning, CodingTeam was an attempt to provide a good forge to the French-speaking community, and we can see that 67.87% of the users are from France. Other well represented countries are Belgium (8%), Switzerland (6.67%), Brazil (2.67%), Germany (2.67%) and Slovakia (2.67%). There are also users from Australia, China, Czech republic, Ireland, Madagascar, Russia and Vietnam. Therefore, it's an international project, although we can bemoan the lack of users from United States, United Kingdom, Spain etc. Note that we know a few users from India too.
It's interesting to take a deeper look to the SCM usage question. We asked if our users were using a (distributed) version control system or not, and which one. It appears that 21.34% of the interviewed CodingTeam users don't use an SCM. Thus, we can conceive that the work we did on the HCI allows users who are not developers to use our software forge: translators, graphic artist, packagers… It may be the sign that we successfuly created the easy-to-use interface we wanted. The others 78.66% are using various systems:
- Subversion (50%)
- Git (21.43%)
- Mercurial (16.07%)
- Bazaar (5.36%)
- CVS (5.36%)
- Darcs (1.78%)
It also appears that 33.96% of users discovered the project by a friend (many thanks to them!), 28.30% by a project using it, 20.75% by a news article and 16.99% by an Internet research.
On the communication subject, we asked our users how they want to be advised of project news. Thus, 59.375% of them would accept to receive a newsletter from time to time. This may not be done because of the large 40.625% of our users that don't want at all. It's also interesting to see that only 54.69% of our users knew that the CodingTeam blog exists, the others just ignored it!
Thereby, our users give a rating of 6.52/10 on the quality of our project communication. We already know that it was one of our weakness and we will take into account the remarks made by them, like:
- the usage of the French in addition to English
- modernization of the appearance
- ATOM feed (hey, that already exists, just follow these news, man!)
- interesting tutorials/links
Another user complained about the fact that the communication is too oriented toward the group of French-speaking people on the XMPP chatroom. This can explain the large majority of our users from France. We should focus other countries and languages to reveal our software forge across oceans!
It's very interesting to know that the CodingTeam software forge is mainly use on CodingTeam.net (73.69%), but it's also used elsewhere:
- users own forge (19.30%)
- forge installed for a single project (3.49%)
- companies (1.76%)
- research laboratories (1.76%)
Our users seems to be satisfied with CodingTeam! The software forge gets a global score of 7.75/10.
The translation system is rated 6.55/10 (the next release will bring a few improvements as the reduction of the loading time). The bug tracker gets a 6.88/10 (again, the next release will bring improvements like pre-selected filters). The documentation system is rated 6.50/10 (users seem to don't like CamelCase and ergonomics).
The top rated features are the SCM support (7.29/10) and the communication tools (7.13/10).
The feedbacks sent by our users are also very interesting. Most of the opinion are positive (encouragement, congratulations) and a few features requests.
It is not surprising to see that among the 39.44% of users that are using another software forge, the most used are Launchpad and Teamforge/SourceForge.net (both 18.42%), followed by Redmine and Trac (both 15.79%), Github (10.54%), InDefero and FusionForge (both 5.26%) and BitBucket, CodePlex, Google Code and Savane.
We asked for the opinion of our users on certain probable features for the future of the project. Here are the podium:
- more statistics (27.45%)
- unbelievable technology from outer-space (26.47%)
- agenda and calendar (25.51%)
- website hosting (21.57%)
A lot of work have been done on the development version of CodingTeam on the statistics. We are glad to announce that projects will soon benefit from detailled statistics! The current stastistics page will be extended with a global activity report (commits, bug tracker, forum topics, translations and documentation in a table and a graph), and a source code analysis!
We also plan to send someone in space to bring back a piece of magic Moon rock, that will give us the ability to provide a software forge for galaxies and mice!
More seriously, our users asked for a few features, like:
- ability to fork a project
- installation script (planned)
- work on the appearance
- German translation
- API to communicate with CodingTeam
- overview: late bugs, notifications
Among these features requested, some will be part of the next release:
- Git (it seems to be more popular than Justin Bieber)
- timeline by developer
- teams associated with projects
Finally, we collected a lot of useful informations on our users and how they see and use our software forge. I also started to develop what users have asked in this survey. So it was very important to take the quizz, and again, thank you all!
See you for the next release!
If you are following our French-speaking community, you should know that a meeting of CodingTeam users have been organized in Paris this week-end. The goal of this meeting was to meet users, discuss of the CodingTeam software, problems, and ideas for the future of the software forge. And to eat a lot of flammekueche (and perhaps too much).
A few technical points have been discussed. We talked about Git integration in CodingTeam (expected very soon), download count, popularity calculation and the possibility of integrating PubSub. We (or some of us) also talked about beers, horror movies and a lots of other fun stuff.
Furthermore, this was an opportunity for five users of the CodingTeam software forge to face their favorite administrator and their favorite developer: me.
This meeting is born on the forum and there surely will be a lot of meeting again in the future!
About 5 months after the 0.9.2 release, the new CodingTeam release is now published! CodingTeam 0.9.3 is together a bug fixes release and a major feature enhancements one as it introduces four great new features.
First of all, CodingTeam now opens to several SCM and supports Mercurial as well as Subversion. From now on, you can create Mercurial repositories inside CodingTeam and they are fully handled from automatic creation to browsing. We are open to all remarks or bug reports on our first implementation of a decentralized version control system.
The second key feature is the evolution of the dashboard. It's no longer just a tool to gather all the timelines of your projects, although you can always do that. It's now a tool to administer all your projects! It comes with a complete administration panel allowing you to do in just one place all an administrator can do on his project:
- managing versions and milestones
- managing access rights
- enabling or disabling features
- uploading files in a project briefcase
- managing downloads
- managing internationalization
- managing news
- managing chatrooms
- managing screenshots
- editing or deleting the project
That means that all these administration tasks are now all grouped in only one place, facilitating their usage. It comes with the support for advanced access rights (you can now finely configure the rights granted to someone), for features management (you can enable or disable a feature that you don't want to use for the project) and for project briefcase (you can upload files to be linked elsewhere, like in the wiki documentation).
Another important new feature is the private messaging system! Users can now communicate between them through the forge. It's simple, you can send a private message to someone in just one click. Private messages are displayed in threads and threads that contain new messages are shown ahead. It's a fast and easy to use tool to improve communication between users.
Finally, the last major feature enhancement for this new release is the notification system. It can send notifications to user when they receive private messages, when there are activites on a bug in which they are involved or on a forum topic in which they have participated. It works both via e-mails and XMPP. Thus CodingTeam reinforces its position as the only software forge to integrate a lot of functionnalities of XMPP (chatrooms, presence, authentification and now, notifications).
Furthermore, we can pick out little improvements like the new pagination system, the fact that CodingTeam is now PHP 5.3.x ready and the bug tracker evolutions (issues don't have anymore to rely on a version and 3 new filters have been added: priority, title and content).
We can also speak about the translation system, which was integrated in the previous release. A few bug fixes and improvements have been made on it, as it was planned. Now, translaters can use the fast submission tool (it allows them to translate a lot of strings on only one page).
And, last but not least, a total of more than 25 bugs have been fixed that we can sum up:
- global administrators are now warned when a project is added to the queue
- project admins are now warned when their project is validated or deleted
- private project's SCM repositories are now unattainable for anonymous users
- ability to download a patch from a diff view in the code browser
- ability to answer on a closed (and tagged as resolved) bug report
- fixed downloads problems
You can download CodingTeam 0.9.3 here. If you were using CodingTeam 0.9.2, you have to read and execute scripts/miscellaneous/upgrade092-093.php to update your database. You might also take a look at our documentation.
And to celebrate this new release, CodingTeam.net has now a very new appearance with a special CSS, thus it will be easy to distinguish CodingTeam.net from other CodingTeam instances at a glance. Enjoy!
A few months after the 0.9.1, the new version of CodingTeam is released! This new release comes with bugfixes and four main new features.
CodingTeam 0.9.2 reintroduces the gettext-based online translation system. It was already in our forge up to the 0.42 but this had disappeared with the full-rewrite of the 0.9. Now, you can easily translate your software online with CodingTeam! The process is simple: you upload a gettext translation model (a .pot file) and then users can translate all your strings in their language. If you already have a gettext translation file (a .po), you can upload it to automatically translate all the strings in the database. When you want to get the translated strings in order to release your software, just export the translation file for all available languages and it's done! And by the way, to prepare the next release, you will import your new .pot file, which will cause the automatical update of your strings database (deleted strings will be deactivated).
This feature is very new and we release it early to get feebacks on this implementation, in order to make it better and better with the time. But here it is, you can now translate your softwares with CodingTeam!
An another main new feature of this 0.9.2 release is the advanced user-rights management by projects. Project's admins can now grant powers or not to their coworkers. For instance, you can now make a moderator for your forums that cannot use Subversion. You can also disable the rights for the others project's admins to edit or delete the project. All you could imagine by the past can easily be done, now!
The third important improvement in this new release is the ability to filter bugs on a multiplicity of criterias. Bugs can now be filtred on their status, type, assigning, version and/or milestone.
And, last but not least, the fourth main feature is the support for multiples templates themes. CodingTeam now comes with two CSS, the default one and a simple one that just aims to show you an exemple of the CodingTeam CSS creation.
Besides that, a lot of bugfixes have been done and we can highlight a few little improvements:
- if need-validate is enabled, when an admin adds a project, he doesn't have anymore to validate his new project
- when a project's admin edits the bug's properties, he doesn't have anymore to inevitably assign it to someone
- if the default versions ordering doesn't fit to your needs, you can set a position identifier to easily choose the order
- ability to prevent anonymous users to post anything on the forge
- spam filter (based on the content)
- a personal dashboard: timeline for all your projects
You can download CodingTeam 0.9.2 here. If you were using CodingTeam 0.9.1, you have to read and execute scripts/miscellaneous/upgrade091-092.php to update your database.
And to celebrate this new release, CodingTeam.org introduces the CodingTeam Blog! Click here to read our blog.
Only 6 months after the 0.9, CodingTeam 0.9.1 is now released!
CodingTeam 0.9.1 introduces:
- basic template system based on the alternative PHP syntax
- ability to make a project private
- advanced commit hooks: it can now automatically close a bug if your commit message contains something like "fixes #id" or "fixed #id"
- new timeline: no more ATOM agregator but data is now taken from the database in a given interval and can be configured very simply on the user-side
- ability for anonymous to report a bug or add a comment to a bug
- notion of milestone in addition to the affected version: roadmap is now generated with the milestone field
- user's briefcases: allow users to upload files for their project (eg: pictures or PDFs for wiki pages…)
- ability to make the forge non-public (require authentification)
- new Subversion code browser: faster and more efficient (can show an image, show a really beautiful diff…)
Also, this update comes with many fixed bugs and little improvements.
Some work has been done on sessions too. For example, developers can now extend the BaseSession class in order to allow different authentification methods inside CodingTeam. This new feature has been used to implement an experimental support of the XEP-0070 (Verifying HTTP Requests via XMPP, a sort of XMPP authentification).
In addition to this, CodingTeam 0.9.1 introduce a security fix that try to prevent session hijacking.
Still on the developer-side, the error handler class has been greately improved. It can show a full traceback (debug and source code). It can handle all errors (from CT errors to PHP fatal errors). And it can also log all errors into a file (the log levelling is configurable).
Administrators will see that their administration interface has been improved too. They can now clear the whole cache just by clicking on a button. And they can edit all data (licences, languages, categories and available translations) with a really simple form.
In order to celebrate this new version, codingteam.org has been upgraded! Feel free to take a look at this website and to spread it worldwide.
You can download CodingTeam 0.9.1 here. If you were using CodingTeam 0.9, you have to read and execute scripts/miscellaneous/upgrade09-091.php to update your database.
Stay tuned, the 0.9.2 is our new goal with a lot of new exciting features. Take a look at our roadmap!
|1 2||1 → 10 of 13|