We now have a lot of good applets available (thanks to all devs :)). This is a very great thinks, making Awn very exciting :)
![[Q]](engine/grafts/newdefault/images/qq.png "Click to quote this passage; Click again to jump to bottom")
But we'll have to face problems with all this devs. We have many applets, some stable, some "work in progress", some in awn-extras, some in the forum ... It's a little messy :)
We'll have a easy way to install python applets (with drag & drop to awn-manager), so there will be no need to host all applets in awn-extras. This installation mode is good for community, testing etc ... but if we want to ship applets with Awn (Official release, packages for distributions ...), we need to host & build them to awn-extras. (For example, gnome-panel ship a lot af applets in default).
So, this is my idea to organise the workflow with applets dev :
- Hack your applet
- Tar the applet, ship in forum, websites ... for mass testing :)
- When you think is good enought, make a blueprint on awn-extras with a link to it
- Awn dev can test it, make the build system up, and place it in the official repo if they think it's a good applet
- Applet dev start a new release, hack the applet etc ... the circle begin :)
Note : this is for python applets. For C, replace "tar" by "branch the bzr repo".
- Hack your applet
- Tar the applet, ship in forum, websites ... for mass testing :)
- When you think is good enought, make a blueprint on awn-extras with a link to it
- Awn dev can test it, make the build system up, and place it in the official repo if they think it's a good applet
- Applet dev start a new release, hack the applet etc ... the circle begin :)
Note : this is for python applets. For C, replace "tar" by "branch the bzr repo".
This is only a beginning of thinking, fell free to add comments :)
