.
Annunci online

All that comes in the mind of an italian guy moved to california
TECNOLOGIE
2 novembre 2008
Technologies:AROS: Going at a higher level of involvement
Well not one of my deepest posts today, more kind of a maintenance one...

Contributing to an open source project is - or at least should be - also a social moment: several people work together in their own free time to a common interest and a common goal. Things might be a bit more complicated when all the working people is scattered around several thousand miles between americas, europe and australia.

Let's tell the truth: if internet did not existed, probably not even open source communities might have been existed, or maybe not so much of it  and widespreaded as they are now.

The working and cooperation instruments are surely less evolved than the ones that can be found in a professional working environment, well not true: i used svn and vim in a recent task at work, and used eclipse in another; anyway, usualy many communication problems got solved through mailing list, instant messenging and IRC.

Despite IRC is considered "out" from new generations, is still a very useful and interesting instrument for group chat and talking.

i mention IRC because in the latest two weeks had occasion to find the "IRCous" skills of pidgin, my default messenger and miranda, the backup one; therefore i have been able to connect quite regularly in the official AROS channel; there "i seen things you humans cannot imagine", if i want to be geeky and cite Blade Runner...:)

It is quite exciting to talk directly with someof the most important AROS system and software developers such as Michal Schulz, Maag^da, Stanislaw Szymczyk and the others.

See Maag^da introduce its new Autodoc for AROS, having Szymczyk and Schulz talk "live" about the latest developments in their own bounties (congratulations, Stanislaw: the bounty is almost done!) and exchange with them ideas and opinions - despite is not a new thing anymore and despite i haven't been an avid IRC user but just a casual user before - is a step forward from being a simple forum lurker and an avid news reader: it makes you "be there" and get some job done actively.

I just downloaded LUA for windows and started to give a first look in SDLBasic, knowing the latter attempts of Mazze in porting it under AROS (with no avail at the moment). I also collected some ideas for some script applications i would like to do, not world changing utilities but still something...

[edit: i gave a first look at the zulu documentation: the lua/mui interaction look quite basic and low level, i sincerely hope to understand something on it; by the way, considered that i have to start from scratch, hope that in the next future will get i better...]

I am also trying to understand how to build some window themes, once i will find the way to make my virtual aros-box communicate with the network.



TECNOLOGIE
11 ottobre 2008
Diary: Technologies: AROS: Opinion: Alternative OS HELPS Open Source, and Linux too.
[Warning: this topic has been left open for whoever likes to add contributions to it]

It's my intention to start DIGG the english section, maybe will help to spread my opinions and make something more happen... Last Saturday I found a link in linux.com pointing at this article on pingdom about the ten most interesting alternative Operating systems in the future: as you can see, at the first, sixth and seventh place we have three Amiga OS-like systems: AOS4.1, MorphOS and AROS;

Beside that, something make me feel perplexed; i already mentioned it in this blog, but guess the time is come to talk about it again.

It is interesting see as still many modern Amiga and Morphos Users consider AROS a kind of resource waste, even despite aprts of AROS code got used for a variable amount of time both in MorphOS and in the new Amiga OS 4, not to mention AfAOS.

And instead is interesting to look as other alternative systems, as Haiku and ReactOS, beside their own problems are getting more aknowledged outside their original niche: it is quite understandable why: both are a valid and open alternative to their closed source counterpart and both are much more user-friendly than even a nowadays linux: beside the old rust between ReactOS and the Wine team for an unfounded topic, the environments are much more peaceful than the "holy wars-ridden" Amiga OSes territories.

And full rivers of words have been written, even in amiga forums, in how AROS allegedly denaturated the original Amiga OS philosophy and look and feel taking ideas from some linux and windows user interface guidelines: then, looking a bit closer in os 4.1, some similar things happened even there but nobody still noticed it, just add a ReAction wrapper and everything is accepted...

But today i dont want to rant about the usual Amigaland mess.

I guess is pretty clear that all the hype around free software has become more than a philosophy: Since money started to run around Linux in the server market the free software transformed itself in a political matter, with internal fights and different -- sometimes opposite -- ways to look at the open source: form the Stallmanian obsession for the purism to the Novell conduct, all surrounded by ego trips and currents: just think at how Kernel programmers are criticizing Canonical for not contributing enough to the Kernel (despite the fact that Canonical is working to improve the final experience for the user and in the desktop development); by the way the programmer criticizing Canonical is working for Novell, and Novell is considered as a Betrayer for their agreements with Microsoft on some patents that MS might decide to enforce against Linux.

By the way, speaking of zealotry, is not known to everybody that last January 23rd 2008 Stallm,an itself has "excommunicated" [EDIT: ok, that is a big word, just removed aros from the link list] AROS because of its requirement of using proprietary roms in UAE and about the recommendation to find them through the purchase of the Amiga Forever package: here is the original mail from AAron Digulla as appeared in the Developer Mailing list:

Hello,
Richard Stallman just let me know that they deleted the link to AROS on their link page (http://www.gnu.org/links/links.html) after I had a longer discussion with him.

The reason is that they only want "free operating systems that have a *policy* not to include, or *recommend*, non-free software."

In our case, we recommend the use of "Amiga Forever" which is non-free software (it contains the Amiga Kickstart ROMs) on http://aros.sourceforge.net/documentation/users/applications/euae.php which means we are in violation of the GNU philosophy.

I had a longer discussion trying to figure out what is going on and the net result is that we're in a similar situation as Linux which can run MAME but Linux doesn't advertise MAME but we do. I'm not sure if it would be worth the effort to delete this page or to move it into the E-UAE package. It feels hypocritical to me to behave as if we didn't recommend UAE while we do recommend it for stuff that doesn't run on AROS itself.

Richard, of course, has a very strong opinion about this and I guess you can't change the world unless you are ready not to make concessions.

So if that topic comes up on AROS-exec or anywhere else, keep a cool head, don't flame Richard or the GNU guys, handle this professionally. I'm not very happy with the decision but OTOH, I doubt that we have many visitors coming from gnu.org (especially since only two other OSs are listed there) and no one will probably even notice the change.

Furthermore, Michael Battilana from Cloanto is actively supporting the Amiga community and us, so I think recommending his product is the least we should do.

And, if we see it with a cold mind, is just a taste of the aforementioned politics. [EDIT: Thank God, the community does not consider follow GNU guidelines strictly a priority nor is important for AROS cause so far things have been handled professionally and business went on as usual].

Sometimes i also have the sensation that several people in the Linux community thinks that developing alternative open source operating systems might be considered a theft of resoueces from what looks like is been decided to be a full focus on linux and other linux-like ooperating systems and distros. The comments in the Pingdom thread gives quite a good overview on the general opinion, defining alternative systems as "Windows 9x bad copies" (even the Amiga Oses:P).

Many of those that wrote the comments by the way, comes from new generation computer users, grown up with windows or linux and of course ignoring or considering obsolete other operating systems before; it is clear as they don't see any need or reason for something different: i might say they don't know there might be something different.

And so they not even understand as the simple existence of other operating systems in the open source universe is important: so as AROS and other alternative systems are using and re-implementing code from linux so the opposite - linux using code from Aros and other alternative systems - might happen and sometimes is happening; in example ReactOS adn Wine exchange code between themselves for a better Windows compatibility and even Amiga OSes got benefits from Linux code: the old ixemul the newer CigWin, most recently even Netsurf, a browser born in RiscOS and ported even on linux under GTK; linux can also benefit using in its code - when the license allows it - code from ports under AROs and other alternate systems. The existence itself of other options "non-linux" beside linux and its distros is a basic part of that "freedom of choice" professed by advocates and one of the essential characteristics of the Open Source philosophy: every one choose its "weapon", the one that fits best with its own modus operandi and how to deal with computing.

Also, the know-how of different people turn out to be good for the operating systems technical exchange.

I already mentioned in past the Kickstart Replacement Bounty phase I and wrote about the assignment to Bheron.

That is all that is shown in the bounty description under the power2people web site: i admit that surely does not look exhaustive. This because, according to one of the developers, the feature showing the bounty assigned coder bio has not yet been implemented.

So, through the comments to the assignment in aros-exec at last it has been possible to know the identity of Bheron. Its real name is Gregory John Casamento and this is the bio from the aros-exec comments:

I've been doing software development for about 18 years. I'm currently an independent contractor.. I own a small company called Open Logic Corporation (not the one at openlogic.com, they took my name 6 months after I got it). I'm currently the chief maintainer of an FSF project called GNUstep, you may have heard of it. ;) I've done everything from C, Objective-C, C++, Assembly on x86 and 68k, etc etc. I was a proud Amiga owner when I was younger and did a lot of C programming on it before Commodore went away. I'm glad for the opportunity to help AROS out. :)

So looks like he is got a great resumee and reliable competences; i put in the links its personal blog in order to follow its progresses on the bounty, if he decides to talk about it.

I will keep this article open in order to add any further precisation and comments to come.
TECNOLOGIE
11 agosto 2008
Diary: Technologies: AROS: There is still something i did not bothered to talk of?

(picture from ok-cancel.com)

I am not in my best condition recently.

I am a bit late in my work schedule, have an acid reflux that make me feel like having a frying pan inside my stomach, and that makes it difficult to focus on my stuff.

I just read the continuation of the goodbye therad of Dammy, ex moderator of Team Aros, in this link on Moobunny and i feel a bit discouraged.

Dammy decided to take out the frogs in the throat in a quite harsh way: will cite its words specifically:

1. Worshiping PPC as the second coming is retarded. It's a failed desktop CPU arch, get over it already. Yes, it's viable as embedded CPU SOC, but that isn't an Amiga by any stretch of the imagination. Dare I say, SOC is the anti-Amiga if I ever heard of one. Unless PPC can lead us to a $150 laptop, it's a dead end. Amiga community made a huge error and it's paying the price for failing to see where PPC was heading off to. If they can make sub $150 laptops, PPC folks should be easily be able to make $50-$75 desktop/server box. Let me further define this, I'm not completely against AROS being ported to PPC. I had finally agreed for TeamAROS to accept a bounty for an EFIKA port (and then SAM440 port) because it would open the door for more developers and possible funding by OEM It is just one of many steps that AROS needs to grow into a viable modern OS to support many archs as possible. ARM should be next to be ported.

2. Lets talk another retarded decision about worshiping 3.1 API. What really drove me away was the brain dead decisions in sticking with a elderly API. The only arch that AROS can reasonably stick with 3.1 is AROS68K because apart of that API has to do with Amiga gfx. Amiga was the fore front of OS development in it's time. C= would have changed the API by now had they survived. Deep down even you know that, I know that, everyone knows that except for the 3.1 blockheads. Yeah, AROS would have been harder for some to port 15 year old software but it's 15 year old software, get over it already. AROS needs to be here and now and ready for the future not living in the past before it was even born! Cargo cultism at it's finest. If I absolutely had to run a old Amiga program, I would run it in UAE. Bill Gates has won, AROS is crippled.


By the way, Dammy is scrupolous in point the NON-developers as guilty on the fully featured 3.1. API compatibility: probably lots of them are notalgic people that strive for a "full immersive" AROS experience at the level of the old Amiga os to revive the "magic" and wake up from a 15 year long nightmare.

In my own, i really hope that AROS will accomplish the full 3.1 API compatibility soon and also hope that the goal will be a new start, not simply the end of line: honestly i don't care if we will reach the point where API needs to be broken in order to add new functionalities as protected memory and old applications might need to be sandboxed [run in a sealed memory area in order not to bring the system down with them in case of crash: the name comes from the sand box in the kids playplace] to run.

Well, not too much things to comment about: the AROS world, so as the actual Amiga/MorphOS world is a bit sleepy, like a country town: a lot of stuff are homebrew and made under the hood: to see how the engine is actually built and things are progressing helps a lot to be subscribed in some developers mailing list.

Sometimes we have nice bursts: the debuto of the Sam440 version, the new nightly builds that now are supporting GRUB 2, guaranteeing a better compatibility and let the system boot even from SFS partitions not only FFS; the EFIKA port where Yakumo9275 and Michael Schultz are working on parallel; the interesst for AROS from the Natami project developers, which should bring finally at a 68k platform port for AROS, and i already see the bounty assigned to bheron, but have no idea who this guy is: info anyone?.

So, in this small town the atmosphere brings to clash egos and well estabilished habits, in  the form we already know such as allthe usual arguments, missed implementations and integral convinctions on fighting between the different Amiga OS-like incarnations.

I don't think to be immune from it, would be superbous sayng so, buit at least i try to have a better real world oriented mindset toward the topic.

Might be that both me and Paolo Besser (just become a father so my congratulations) are ,in different ways working and struggling to make AROS grow beside the simple hobbyist operating system, as some of its own developers think still about: we are convinced that the Amiga architecture still has a very noticeable potential, especially in some hobbyist sectors, as support tool: since not all uses of an OS require protected memory and other advanced features, there is a way to increase the userbase beside the ex-amiga user and occasional developer/lurker: think in example at HAM-radio, at music sequencing software with MIDI enabled trackers and other open source software as audacity.

As I said on this thread (in italian) on Amigapage.it:

I see interesting openings especially for those hobbyist fields in which people prefer to focus more on the computer as help than as an additional instrument to be handled and tuned apart from the rest: i remember some applications for HAM radio on amiga, some lighting software (and i remember sources were released some time ago) and for other DIY sectors where is not required to have a fully modern operating system, needs to be simple to be used and configured and, considered that viable alternatives for those people are, for now windows or linux: both quite bloated and/or difficult to be configured/maintained and both requiring quite powerful hardware and a good amount of RAM: unlike those, AROS looks perfect: is lightweight, can be used in fairly old machines and is easy to handle.

Well, beside this, what else I did not bothered to write on? About Rapid Application Development tools to help the development of applications, something which all amiga flavours but specially AROS are lacking: for AOS 4 we had the no longer supported ADV, so some developers are trying fo till the gap. One of the developers of AROS, gianfranco "Shinkuro" Gignina, asked about an opinion on this kind of tools show a partial disagreement:

I personally find automatic GUI creator tools as something discrete for beginners and professionals on deadline. In some other cases I consider the automatic GUI generation tools a sort of gambling, which I would not use for serius programming.... i might add some real life example as Visual C#, that, when you use the tools does links and instantiate all GUI elements in one method, something that, once referred to OOP programming, based on extension and inheritance looks at least obscene....

..and not to forget that on Amiga Programming, the tool code and the GUI code cannot be separated as in more modern operating systems as cited by Shinkuro in this other thread:

There is no complete OOP API set on Amiga, that has been done only the GUI so far.
The Frying Pan author, to make its own life easier and transfer code faster between Amiga OS flavours, created this:
http://sourceforge.net/projects/amiga-generic/

I think the link above might be quite interesting but, since has been released under GPL 2 license, i personally have no idea whether there might be any problem in using it iside AROS, maybe can be used for applications, and not for OS components...

It is also not possible, IMHO, to divide the GUI development thread from the GUI usability thread, that are actually the pain-in-the-bottom of most open source projects; some recent and less recent studies and considerations here and here let us know how the base problem is sometimes coming from the open-source environment nature itself (this is mainly related to linux operating systems, by the way) and the fact that coders does lack the skills - a subset not easy to achieve - to build usable interfaces.
 It is not completely their fault: writing an usable application requires nontrivial efforts and sometimes an application has to be designed to be usable since scratch. Plus usability is not an unniversal rule, is something that is quite subjective: what is usable for a developer is non usable from a graphic artist and vice versa plus what might be usable for those two categories might be hard to understand if not completely usuitable for an average user...

In the closed source world software usability on an OS is ruled by interface guidelines (something that GNOME and lately KDE started to adopt too) and improved by tests and feedback from users: - for what is concerning the first one, related to AROS, Shinkuro proposed an Interface Guideline reference on the developer list to improve the existing 3.1 guidelines, with not too much success so far;
-the latter one instead is undoubtely expensive, therefore hard to be put on practice from an open source project if not backed up from some capital: lately i learned about the existence of an open source usability project:  openusability.org, maybe can be useful.

Another problem for the open source application usability is the subculture hacker environment where some of the developers grew up: a very closed environment, almost a sect in which the initiation ritual is to understand and master the operating system and its application, deep to the inner workings an ddo the leap from "luser" to "l337": that might give an hint about the still scarce desktop penetration of linux: those topics are part of the bread-and-butter of the linux haters blog, and also this older but still interesting article shows how the supposed "lack of respect for the fial user" might be reconducted sometimes in the well-known for amiga users ego clash and its consequences, not alone the "leaving the playfield bringing all the toys with him" bad attitude that killed or hamed badly old software projects, including poseidon and MUI, instead of give the community the possibility to mantain and make grow opening the source: i know tihs is personal decision  matter but sometimes the reasons to screw up projects are so trivial or inconclusive that might sound like tantrums.

I hope to give a nice help to developers willing to improve software usability in linking this usable software small handbook from joelonsoftware.com: not to be considered an all-in-one course but a good start to improve the development method.
TECNOLOGIE
17 luglio 2008
Diary: Technologies: AROS: Guess i did not got this Open Source thing yet?
[This article translated in a latter time]
Originally published in July 17,2008

[EDIT: Aobut KDE 4 and on how final users are acting and expecting as consumers is also mentioned here.]

The latter interventions on it.comp.os.amiga here (google translated), concerning the coming soon Amiga os 4.1 and the recent discussions shown on linuxhaters blog here and on linux.com here makes me consider on how probably i misunderstood badly the motivations behind ther open source movement: I always thought at social motivations as the need for computing tools for who cannot afford to get a closed source operating system or applications, i thought about humanitary and non-profit organizations support, learning and start-up tools for third world and underdeveloped countries, beside the intentions to disconnect the IT from the traditional software and OS industry, the knowledge share and the opening of algorythms and libraries available to everybody for any purpose, without the need to quit the project or being forced in pay royalties for quite banal algorythms.

Maybe am still too naive and idealist: it is sure that, once somebody reach an age close to 40, having a reality check is quite painful ot handle than when young.

And i can also understand the hatred of linux hater and the strong frustration of the newcoming linux and AROS developers, to mention a project which am emotionally tied at.

Things as reading here on how
TECNOLOGIE
9 luglio 2008
Tecnologies: AROS: the Pidgin Factor and Product Management
[This article translated in a latter time]
Originally published in July 9,2008




[EDIT - oct 20 2008: this article is quite old, but seems to have grasped well some AROS recent ongoings so give it a read]


Unless somebody else of the Cannocchiale bloggers don't tell me how to recover my old unpublished articles (waiting for time, inspiration, further documentation,etc.) i feel kinda forced to start again this article, with the needed updates.

First of all, let me introduce the "causus belli": Pidgin Bug Report, an article on Product Beautiful and a further Article on Product Beautiful on the subject.

The outcome is surely known on who is following open source software progress: since last jannuary pidgin users are complaining about a new feature that resizes automatically the message textfield; the developers answered that it was introduced by them because they liked it and they have no plan to remove it or make it facoltative. A big discussion arised, quite polite but with strong opinions and brought to a riot against developer's decision, at the bug report closure as "wont_fix" and at a fork of the program, funpidgin.

Among all the interventions, one quite interesting from Dan Livingston, teacher of "collaboration in the Open Source world" in a North American college, going quite hard on developers behaviour:

I teach "Collaboration in an Open Source World" at a local college. I have been searching for, and in this ticket have found, a perfect example where communication between open source developers and users fails at multiple, fundamental levels.

Obviously, the motivations of open source developers are varied; some do it for technical enjoyment, others enjoy knowing they are contributing intellectual capital to a better world. The problem is when the motivations of open source developers conflict with the expectations of users.

Consider every wildly successful open source project: the users are enthralled with their ability to perform new activities in ways previously unimagined. Rabid dedication grows, and an evangelical fan base results. Pretty soon, it's obvious why users would not want to go with non-open source software alternatives.

What happens when those same newfound powers are taken away? What happens when the developers impose their personal dogmas upon the project? Even for as small an issue as chat window resizing, a minority (or majority) of users will emphatically express dissent.

It's easy to see why open source developers could develop dogmas. Some like to fantasize about the theoretical limits to which a design may become "pure", developing a vile repulsion to anything which steers away from purity. Others become obsessed with metrics such as maintenance effort per line of code, even though they often worry about features and lines of code which only contribute to 1% of the complexity of the application. Yet others develop fixation on "ultimate user simplicity", feeling that two options are better than five options which deliver more power. The most dangerous dogma is the one exhibited here: the God feature. "One technological solution can meet every possible user-desired variation of a feature."

The initial lure of open source software is that quality software should resoundingly meet the needs of users. As demonstrated up until Pidgin 2.4, the fan base has emphatically been extolling the virtues of Pidgin. But when developers take a feature away, presumably to implement a "better version", and that better version in fact is a step backwards from the functionality previously available, they had better have a damn good reason. Such a reason is lacking here.

"This is how IM should be used." "Our design is better." "We will only consider a 'pure' design in which we can accomplish the old functionality in a paradigm that also supports the new functionality." "An additional checkbox is too detrimental to the user interface." "Maintaining two branches of logic within the dialog sizing component will be untenable." "We have no interest in not pushing our shiny new object."

These are all statements, which if executed within a corporate arena, would get developers fired. Developers, make note: you are doing a disservice to the community you claim to represent, and are doing so with false illusions that you are "right" because you have convictions in your justifications.

It does not matter that you are open source developers with the autonomy to ignore your user base. It does not matter that a plugin "could" be developed to solve the problem. It does not matter that you feel your default solution is superior. It does not matter that you only want to consider solutions which can be implemented through the new solution framework. It does not matter that your users should abandon your product if they don't like it. It does not matter that someone could fork the code base. It does not matter if 11 thousand people download your source code per day, and only 270 complain about it. For each of these, there are very valid rebuttals.

So, only 270 complaints for this feature, out of 11 thousand downloads? How many people immediately uninstalled the program when they realized it could not longer do the simplest functionality that GAIM and other IM agents do? How many don't know that they are using software that is now crippled in comparison to its former flexibility? How many use the software today, but will switch to GAIM tomorrow when they hear from their friends that it's so much easier to resize in GAIM?

The fact is that typing letters into an IM window is THE most critical task of an IM program. Users have varying needs, needs which can not be addressed by your limited attempts to come up with "one solution for everything" that incorporates "shiny new logic" that demonstrates how smart you are. You are ignoring the fan base with a dedication to your convictions that is alarmingly evident to even the most unobservant of followers, and as such, you are demonstrating that you no longer deserve to be in the position of servicing the needs of your user base.

For the sake of everyone involved, I hope you find your path back to the light.


And the following is the hypothetical response that Dan supposes users should receive from the development team:

Dear Users:

You are most undoubtedly reading this page because you want to know how to manually resize the text input area in Pidgin. It is a feature that you have perhaps grown accustomed to and comfortable with, but please make note - this feature is no longer supported.

We have received many complaints from a very small minority of the user base who nonetheless persists in being very vocal about their displeasure. Please take comfort in the fact that they are only a very small percentage base of Pidgin users, and if ignored, will go away and bother some other open source project.

Nonetheless, we feel it very important to make the following proclamation regarding on our stance on this project: we will not "fix" it. In fact, please notice that the status of this "bug" is "wontfix". So would you please just get this idea through you head and go away now?

We are developers of this software, and we develop Pidgin so that it may fulfill our explicit needs and desires. If you want to join us for the ride, then fine. Just shut up, though. Please, if we've made a feature a certain way, it's because WE WANT IT THAT WAY. Is that so hard to understand? All day long our bosses tell us what to do. Our wives tell us what to do. Our government tell us what to do. YOU will NOT tell us what to do.

Some say that as the developers of the premier open source IM client, we have a "responsibility" to serve as wardens of our precious charge, nurturing it into a fine, outstanding, model citizen of the open source community. That's rubbish. The last time we checked, we didn't sign up for day care. We signed up to write software that WE want to use.

So please take your ideas and go elsewhere. If you want a development team that responds to the desires of their user base, hoping to release world-class, quality software to millions of people, then start your own open source project. It's not that hard. It's free. All you have to do is commit your time, just like we commit ours.

The development team would very much like to come up with a solution that meets the needs of ourselves and the general user base. However, we cannot understand your needs. You speak in a foreign gibberish, gobbledy gook language that none can understand. "I just like it that way!" That is not an answer! You must enumerate the metrics and aspects of your preferences and desires in ways that we can evaluate and then assimilate into our collective. We cannot currently assimilate any of your idiotic reasons for wanting a resizable text box. And by idiotic, we mean "any solution which does not fit into the scheme of our cleverly intelligent auto-resizing text field."

So, just to make it clear: we will not listen to your suggestions unless your suggestions make sense to us, and we like them. If you do not like it, there are plenty of other ways on the Internet in which you may occupy your time.

Regards, Pidgin development team"


Damn! Me too, when i develop in my job am really tempted to answer like that way but, considered that if i do it might need a new job , might find myself broke and with no way to pay bills, am  kinda forced to consider a more condescending attitude.

Anyway, going to the point, i took out the Pidgin debate because of some attitudes from the ReactOS team in their discussion forum shortly before the 0.3.5 release.

I heard several hundreds of time and am aware that AROS and ReactOS need to be defined "hobbyist" operating systems and not "world domination" systems and also am aware that the "no schedule and rocking" philosophy of AROS developers is not keen to make final users and investors to plan on it; the other side of the situation is that AROS is not enough developed because its low developers number and, paradoxically,  has a low number of developer because is not developed enough yet.

Beside the preaching of FOSS evengleists, the Open Source philosophy does not require a cooperation based on the "code or get out" attityude: as exposed by Dan Livingston above, a open source community expects cooperation even in "minor" tasks such as community activities: feature requests, bug report, advertising, advocacy, graphic themes, etc.

In example I feel that am controbuting writing about AROS in my blog (advocacy): i hope in future to cooperate at a deeper level, wife and job allowing me to do that.

And even an open source community, willing or not, DOES marketing, meant as presentation of it for its diffusion: it does it mainly in a viral way, such as spreading the word, commenting it, etc.

Of course having a more outgoing profile to "sell" helps the copmmunity in the "product" diffusion.

And the diffusion of the "product" brings in both final users and potential developers.

Aros, thanks to its media apperarances with VmwAROS, for its user's advocacy and advertising activities and for the surviving Amiga community that is having benefits through AfAos (AROS for Amiga Os, a project that is replacing outdated AMiga libraries with more recent AROS ones) is actually getting more users and developers; but it's not enough yet.

A better presentation of the project, the rewquired documentation development - that is starting to appear but is still too depending on the pre-existing Amiga OS one, being also affected from the Guru book publishing - maybe the apparitions of written and video tutorials to explain the AROS use and at the end the hoped coming of applications and hardware drivers (tightly tied to the aforementioned catch-22 "lack of developers in a underdeveloped OS") might finally bring AROS and other alternateOSes to be more widespread than they are now.

It is also my opinion that, once a poject reach a "critical mass" of users, the developing team's hobbyistic/edonistic approach to programming cannot be the main motivation and the reason of existence anymore; from the fact itself that users are using and relying on it doing even critical activities with it, the team acquires the moral, if not social, obligation to listen to the final users. Then, if they like to modify things they can "sublet" the maintenance and dedicate themselves to a "director's cut version" aside; then, if the new version will have a good response they can let it contribute back to the main flow and so on; but the fate of the project is no longer in the developer's hands only: the project has become and belong ALSO to the community that embraced it, use it and love it.

Product Beautiful in its article talk about the Product Management in the Open Source community and on how the actual approach - thinking that product management is meant only for commercial activities - is wrong;
As provocation, they propose that open source products should have a "quality seal" in their home page (the one at the top of the page) where developers declare whether the project purpose is toward the community or if the project is made to "scratch their own itch" - meant for themselves - in ordet to avoid bad facts as the ones in the Pidgin Community.

I would be glad to hear firther opinions about this.
sfoglia
  

Rubriche
Link
Cerca

Feed

Feed RSS di questo 

blog Reader
Feed ATOM di questo 

blog Atom
Resta aggiornato con i feed.

Curiosità
blog letto 1 volte

Older Posts

Who links to me?
Get in touch with Simone Bernacchia

 




IL CANNOCCHIALE