[s1mp3-dev] Defeatism and proposals was Re: help me

[Wladston Viana F Filho]

Legolas,

Thanks for the initiative. These are my comments :

The project would really stop if the entire world would suffer a
> permanent electrical powerdown. I don't like this "defeatist" approach. ;)


Thanks for the words!  Although the  web site and forums are growing, we
don't have the same thing on the development side, that's why I said. Things
don't work on our project like on other successful ones, and I don't know
WHY!!!

I propose to move all the website development discussion to the Balzac
> mailing list and to continue it there, using this list only for the Swan
> development. I do not suggest making another maillist because people
> hates having to subscribe to various mailing lists and it would result
> in an excessive fragmentation.


Hum ... I really don't get the point of why our people who want to help on
the content design should subscribe to the balzac mailing list, but ok.

imo, it will happen sooner or later, we WILL have to fragmentate the list,
and we'll have the people on the balzac mailing list to move.

I would create another list (we'll have s1mp3 and s1mp3-dev), ask people
interested to help the non-development work to move. Rockbox works this
way...

But if you the other way is better, say it, and I'll execute it.


Once we separate the website from the product, Swan, I suggest one more
> division: s1mp3 has been offering support up to now. We should use
> support as a "bait" for our project, that is to HAVE a new firmware.


If I got what you mean, we will support the issues of the end users by
asking them to use our firmware ?

It's a good idea, but we have to have a firmware to provide them first ...


Our public presence
>
> 1. WHY the site is called s1mp3 if the firmware will be Swan instead? My
> proposal is to have the next website more Swan and less s1mp3 so that if
> in future (far future) we are going to use a swan-like domain it will be
> more consistent with the content.


Mainly because the project is called s1mp3.org and there could be an
identity loss if we changed it.

I have expressed my opinion to change that some months ago, when I presented
a new project logo, but people did not like it.

2. the next website should be a presentation of our Swan project


tell me ... WHAT are we going to present ??

Have you looked at the new s1mp3.org structure at
http://www.s1mp3.org/wiki/index.php/S1mp3.org_planning ?

The Swan is presented on a page inside the development page. If you have any
other idea, please suggest me.

and
> contain a separate section with the current s1mp3 support knowledge
> base.


The support will be "indexed" on the FAQ. If you have any other ideas ....

We should publish on the website front some friendly pages which
> explain what we are doing while the real development are should be (as
> in continue evolution) the wiki.


this is already done. See the
http://www.s1mp3.org/wiki/index.php/S1mp3.org_planning

the front page is not ready yet, but all the others are compliant.

2.1 Some wiki pages will be editable by developers only and others will
> be public (we have already planned to work on it this way). Most of the
> "static" content temporarily on the wiki (except for technical data)
> will be moved to the main website.


yeah, this is the work i'm trying to do atm...

2.2 The Balzac CMS on top of which s1mp3.org will be rebuilt will easily
> allow add & edit, but *it is my holding opinion to separate web
> mantainers (website) from developers (wiki)*. I also would like to see
> Balzac finished soon to start the _test stage_ and then to launch it on
> s1mp3.org


sure! To tell the truth, balzac is __almost__ mature enough to be used on
the s1mp3.org page.
but the content is not ready. This is why i'm trying to work on the content
these days.


2.3 The objective is to have a multi-content website working as a
> jumpstar for those who want to develop, use our developed software or
> simply get that device working again (in the previous order of
> importance).


okay. But we can't work on a fantasy environment; for now we don't have
__ANY__ developed software end-users can profit of, exept wire's s1fwx and
s1res.

Please, take a look at the current structure :
http://www.s1mp3.org/wiki/index.php/S1mp3.org_planning and suggest changes
...

_But the help we give about Actions' & co. devices must not
> interfere with our main target_ and you probably recall the reason.


surely. 100% agreed. But our 3.000 unique visitors/month come on the website
in 99% of the cases for support, don't forget that.


> 3.1 The simulator. We will need it to debug our software. I suggest to
> freeze the API design until we have a working simulator which can run
> the original firmware and relative applications. By that time we will
> have access to the embedded ICE and we will know enough to write our own
> firmware. So, it is an important excercise that will bring us the
> knowledge we miss about our target hardware


Well - my opinion does not count here

4. push each member into a specific task and start working. We should
> have the project money converted into beer (or vegan food) gifts to the
> active members. No, it is only a joke this time.


:))
When we finally achieve success, we could make a party - all the devs
invited :)


-- 
Wladston Viana Ferreira Filho
Belo Horizonte - MG, Brasil
Visit the project: s1mp3.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://s1mp3.org/pipermail/s1mp3-dev_s1mp3.org/attachments/20060611/4240ce5c/attachment.htm