[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-active
Subject:    Bodega GSoC 2013 Proposal
From:       Giorgos Tsiapaliokas <terietor () gmail ! com>
Date:       2013-04-23 15:39:33
Message-ID: CAODYyLY_505KccUaTGRL_XMqhcppLFAO46XWxBkSeViWRv8Jyw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hello,

this my proposal for the GSoC 2013

My proposal contains(in short) the below tasks

* implement the rankings functionality for the assets in the bodega-server
(1)
* implement a comment system for the bodega system (2)
* add support in our clients(bodega-client and bodega-webapp-client) for the
collections. (3)

-detailed description

(1): The server doesn't support the rating of an asset.
Our system shouldn't use the common 5-star system because
it is well known that this system isn't meaningful

http://xkcd.com/1098/

:)

So our system will have predefined categories for each kind of assets.
For instance the books will have different categories from the applications.

Each asset type will have categories which will map to numeric values
from 1-5.

Also the bodega-server will offer an API in order our clients to be able to
take the data.

(2): The common way for a comment system in a store is this one(check the
screenshot). The problem with this approach is that it becomes chaotic
after a
number or replies and there is no way to take some valuable information
within
a logical amount of time.

So our solution should be a forum. Using a forum system makes it much more
easier to find useful information in a short amount of time.

So we need a forum
*  in which our users will be able to login with their bodega account
*  each participant who has upload an asset in the store will have a forum
and for each asset that he has uploaded a sub-forum will be created.

-technical details

we will use an existing forum system such as phpbb,
in which
* I will implement a json API with which the bodega-server
will communicate and create the appropriate forums and sub-forums.
* make it possible to connect with the bodega-server credentials.

(3): The bodega-server offers an API for the collections(most downloads,
most views, etc) but our clients doesn't support this API. So I will
implement this functionality.

-Timeline

(1) rankings:
-2 weeks for implementing the feature
-1 week for creating the public API

(2) comment system:
-2 week for implementing the login feature
-3 weeks for implementing the public API
-1 week for implementing support for it in the bodega-server

(3) collections:
-1 week for implementing it in the bodega-client
-1 week for implementing it the core functionality in the
bodega-webapp-client
-1 week for implementing the ui in the bodega-webapp-client

2 weeks for finishing the loose ends

Regards,
Giorgos

-- 
Giorgos Tsiapaliokas (terietor)

terietor.gr

[Attachment #5 (text/html)]

<div dir="ltr">Hello,<div><br></div><div>this my proposal for the GSoC \
2013</div><div><br></div><div>My proposal contains(in short) the below \
tasks</div><div><br></div><div>* implement the rankings functionality for \
the assets in the bodega-server (1)<br clear="all"> <div style>* implement \
a comment system for the bodega system (2)</div><div style>* add support in \
our clients(bodega-client and bodega-webapp-client) for the</div><div \
                style>collections. (3)</div><div style><br></div><div \
                style>
-detailed description</div><div style><br></div><div style>(1): The server \
doesn&#39;t support the rating of an asset.</div><div style>Our system \
shouldn&#39;t use the common 5-star system because</div><div style>it is \
well known that this system isn&#39;t meaningful </div> <div \
style><br></div><div style><a \
href="http://xkcd.com/1098/">http://xkcd.com/1098/</a> <br></div><div \
style><br></div><div style>:)</div><div style><br></div><div style>So our \
system will have predefined categories for each kind of assets.</div> <div \
style>For instance the books will have different categories from the \
applications.</div><div style><br></div><div style>Each asset type will \
have categories which will map to numeric values</div><div style>from \
1-5.</div> <div style><br></div><div style>Also the bodega-server will \
offer an API in order our clients to be able to </div><div style>take the \
data.</div><div style><br></div><div style>(2): The common way for a \
comment system in a store is this one(check the screenshot). The problem \
with this approach is that it becomes chaotic after a</div> <div \
style>number or replies and there is no way to take some valuable \
information within </div><div style>a logical amount of time.</div><div \
style><br></div><div style>So our solution should be a forum. Using a forum \
system makes it much more</div> <div style>easier to find useful \
information in a short amount of time.</div><div style><br></div><div \
style>So we need a forum</div><div style>*  in which our users will be able \
                to login with their bodega account</div><div style>
*  each participant who has upload an asset in the store will have a \
forum</div><div style>and for each asset that he has uploaded a sub-forum \
will be created.</div><div style><br></div><div style>-technical \
details</div> <div style><br></div><div style>we will use an existing forum \
system such as phpbb,</div><div style>in which</div><div style>* I will \
implement a json API with which the bodega-server</div><div style>will \
communicate and create the appropriate forums and sub-forums.</div> <div \
style>* make it possible to connect with the bodega-server \
credentials.</div><div style><br></div><div style>(3): The bodega-server \
offers an API for the collections(most downloads, most views, etc) but our \
clients doesn&#39;t support this API. So I will implement this \
functionality.</div> <div style><br></div><div style>-Timeline</div><div \
style><br></div><div style>(1) rankings:</div><div style>-2 weeks for \
implementing the feature</div><div style>-1 week for creating the public \
API</div><div style><br></div> <div style>(2) comment system:</div><div \
style>-2 week for implementing the login feature</div><div style>-3 weeks \
for implementing the public API</div><div style>-1 week for implementing \
support for it in the bodega-server</div> <div style><br></div><div \
style>(3) collections:</div><div style>-1 week for implementing it in the \
bodega-client</div><div style>-1 week for implementing it the core \
                functionality in the bodega-webapp-client</div><div style>
-1 week for implementing the ui in the bodega-webapp-client</div><div \
style><br></div><div style>2 weeks for finishing the loose ends</div><div \
style><br></div><div style>Regards,</div><div \
                style>Giorgos</div><div><br></div>
-- <br><div dir="ltr">Giorgos Tsiapaliokas (terietor)<br><br><a \
href="http://terietor.gr" target="_blank">terietor.gr</a></div> \
</div></div>

--f46d044306aaee350004db08fdfe--


["kdeapps.png" (image/png)]

_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic