Hi all, I were following this thread and I think that the most remarkable post is this one from Martin who resumes the most important things that we want to have in the showroom page.<br><br>I made this Classes diagram [1] in DIA to make the basis for the development of the site. It's really basic but I think that it's a start point.<br>
<br>I'll explain several points to make the diagram clear:<br>* The classes have the attributes that I can figure out from the requests on this thread.<br>* A user can be a maintainer of a distribution/application or just a regular user (someone with account in the page who can vote for the distros/apps popularity)<br>
* The "File" class (table) contains the files (commonly image files) of the three entities: distros/apps (screenshots); user (user image)<br>* The distros and the apps have an attribute to represent their popularity (a float number from 1 to 5) that is set with a stored procedure that update the "popularity" field with the average of the califications of the users for the distro/application (a user only can vote once for an distro/app, which makes the popularity more reliable). The procedure is triggered whenever an user give a distro/app application)<br>
<br>TODO:<br><br>* Discuss if any registered user can edit the information of a distro/app or how it will be covered.<br>* Reppresent the dependencies of an application<br>* Other things that you want<br><br>Note: DIA diagram contains attribute description for each class<br>
<br>I don't know if the diagram is usable/compatible with the apt-portal idea but is my way to bring my two cents for the cause......<br><br>Remember that you're welcome to make adjustments to the diagram in order to make it more representative of the situation of a AppDB for the FR.<br>
<br>Greetings from Colombia<br><br>[1] <a href="http://www.mediafire.com/download.php?kyyzzcuz3kt">http://www.mediafire.com/download.php?kyyzzcuz3kt</a><br><br clear="all">/***************************************<br>* Don't Worry.......Be Linux!!!!<br>
* Cristian Gómez Alvarez <br>* Ingeniero en Sistemas y Computación<br>* Universidad de Caldas <br>* Comunidad de Software Libre Manizales<br>* IEEE/WIE Student Member<br>* Linux User #463617 <br>
* Mi Blog: <a href="http://cristianpark.sehablalinux.com/">http://cristianpark.sehablalinux.com/</a><br>****************************************/<br>
<br><br><div class="gmail_quote">2009/8/21 Martin Jansa <span dir="ltr"><<a href="mailto:martin.jansa@gmail.com">martin.jansa@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Fri, Aug 21, 2009 at 12:13:04PM +0300, Risto H. Kurppa wrote:<br>
> -> Still I think there's a need for a platform to promote ~working<br>
> apps in an appealing way.<br>
<br>
</div>Yes that's true and I think that <a href="http://opkg.org" target="_blank">opkg.org</a> is doing just that.<br>
<br>
Only few small parts are missing.<br>
<br>
1) Use it rather as nice showroom, not as opkg/deb repo<br>
<br>
2) Voting UP/DOWN for popularity and showing most popular packages for<br>
section/task, maybe iven UP/DOWN buttons for "I would like to test<br>
it/use it or I need exactly something like this" - someone please<br>
provide package for my distribution.<br>
<br>
3) opkg/deb or manuall installation instructions only in first phase<br>
when its unknown package from unknown developer :)<br>
<br>
4) then community-editable list of distributions where it works/doesn't<br>
work.<br>
<br>
5) same list with sign if its included in standard repo of that distribution<br>
and if its not included, user should provide a link to distribution bug tracker<br>
where is package request for that application and everyone could provide<br>
bbfile/src.deb as attachment in that bug, its quite easy. Distro<br>
maintainers than could check if that package is really that popular and<br>
if someone from users/developer itself provided working bbfile then commit it to<br>
their branch, remove link to bug tracker and set sign, thats already included.<br>
<br>
Maybe just table like this<br>
<br>
| distribution | works | doesn't work | I would like to use it | Included | Package request |<br>
| shr-unstable | 10 + - | 2 + - | 40 + - | Yes | link-fixed |<br>
| shr-stable | 2 + - | 0 + - | 400 + - | No (_Yes_) | link |<br>
| debian | 12 + - | 0 + - | 4 + - | No (_Yes_) | _add_link_ |<br>
| _add new distribution_ |<br>
<br>
where + - would be voting links<br>
<div class="im"><br>
> > Very last words:<br>
> > Please do not put anything up, when there is no time / resources to maintain it. It would be a shame to waste so much efforts<br>
> +1!<br>
<br>
</div>+1!<br>
IMHO only few improvements of <a href="http://opkg.org" target="_blank">opkg.org</a> are needed..<br>
<font color="#888888"><br>
--<br>
uin:136542059 <a href="mailto:jid%3AMartin.Jansa@gmail.com">jid:Martin.Jansa@gmail.com</a><br>
Jansa Martin <a href="mailto:sip%3Ajamasip@voip.wengo.fr">sip:jamasip@voip.wengo.fr</a><br>
JaMa<br>
</font><br>_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
<br></blockquote></div><br>