Our first submission to the Banshee project was largely successful. The main developers wanted several locations in the code that referred to "banshee-1" to be changed to "banshee" without breaking anything. With a bit of help, we decided how to handle each instance and submitted a patch. The patch has been reviewed and incorporated into Banshee.
We are now working on an extension using Gwibber that will allow people to post statuses to Facebook and other social networks from within Banshee. By default, these statuses will contain metadata for a selected song. In addition, the user will be able to edit the message before it is posted.
I know a lot of people who use both Banshee and Facebook. It is interesting to think that I might see this extension we are writing in use.
For the last few days we have been struggling to set up the project, but the issue has been found: In some builds of Banshee, autogen.sh was still looking for "banshee-1". Apparently the switchover caused a few problems. This has clearly demonstrated the point that even small changes can be hard in a large project. It seems challenging to balance a "design first and code second" philosophy with the rapid iterative development that agile processes call for. I imagine that most large projects require difficult revisions from time to time.
No comments:
Post a Comment