@Goncalo Margalho, calm down. There is no decision made at the moment or anything like that. I also don't think that Strobl wanted to nuke your part of the discussion with a "i'll make some proof-of-concept"-code. If we have code to talk about, we just have a better foundation for a discussion, don't mind him.
Before you go crazy here with that stuff, you should first answer that: What do you guys want from AppCenter? A user opens it and then he sees the newest/hottest/whatever apps with some infos (my guess)? Define what exactly is your target when proposing a radical change to a project (So far no one has answered shnatsel's question about the problem you see in the current AppCenter). Someone want a webpage instead of AppCenter (if i read that correctly)? Why? You should first answer that before going into technical details. 2013/3/26 Chris Timberlake <gam...@gmail.com> > The first decision needs to be "What is AppCenter?" Is it going to be an > App Store or is it going to be just an App Center as it is now? That > decision changes the course of the project forever. An AppStore is a huge > undertaking that should be planned now. > > > On Tue, Mar 26, 2013 at 5:51 AM, Joshua Strobl <truthfroml...@gmail.com>wrote: > >> As I said, these decisions need to be a group consensus. We're not going >> to be the next Canonical. >> >> >> On Tue, Mar 26, 2013 at 5:49 AM, Goncalo Margalho <g...@margalho.info> >> wrote: >> >> If you do everything on your own deciding everything, there's no need to >> follow that. >> Saying that. Good luck with the AppCenter ;) >> >> >> On Tue, Mar 26, 2013 at 12:43 PM, Joshua Strobl <truthfroml...@gmail.com >> > wrote: >> >>> There is a limiting factor on what we can implement from third parties. >>> For instance, with Ubuntu Reviews API, we (along with everyone else) has >>> read-only access, therefore we are not able to apply our own ratings and >>> reviews (obviously a write process). This is already going to be covered in >>> the API, I'll be pushing out code by the end of the week (hopefully) that >>> will handle a portion of this. >>> >>> The general idea is to either completely pull all the reviews / ratings >>> from Ubuntu, pretty much regarding every application (although I'd prefer >>> we only limit to applications that are actually popular) and store them in >>> our own database. This will ensure that any breaking changes that occur in >>> Ubuntu's Reviews API do not affect AppCenter, since the reviews are stored >>> with us anyways. Another idea would be to continue pulling reviews / >>> ratings from Ubuntu's Reviews API and only store reviews / ratings by >>> elementary OS users. >>> >>> It is really up to group consensus. This isn't so much about rewriting >>> things, its more like leveraging existing APIs to get a good jumpstart on >>> an AppCenter. >>> >>> I would appreciate if you'd follow >>> https://bugs.launchpad.net/appcenter/+bug/1091406, as I'll be posting >>> details, potentially initial JSON formatted string files (for showing how >>> some of the data will be structured when being requested via an HTTP >>> Request) and at some point I'll link to the repo for the API. >>> >>> - Joshua Strobl >>> >>> On Tue, Mar 26, 2013 at 3:29 AM, Goncalo Margalho <g...@margalho.info> >>> wrote: >>> >>> So we are going to rewrite it? Why in linux community people like to >>> rewrite things? We need to plan stuff to work on in and then implement. >>> Here, everyone likes just to implement. Why dont we think about the future. >>> Use our brains to build something that it will stay like this? >>> On Mar 26, 2013 10:07 AM, "Sergey "Shnatsel" Davidoff" < >>> ser...@elementaryos.org> wrote: >>> >>>> 2013/3/26 Goncalo Margalho <g...@margalho.info> >>>> >>>>> I think that the AppCenter now is just a wrapper of packagekit, i >>>>> mean, instead of using apt you use AppCenter, how do you add reviews? >>>>> paying apps etc? >>>>> >>>> >>>> No, it's not. PackageKit API does not provide application screenshots, >>>> for example. They're fetched on-demand from >>>> http://screenshots.ubuntu.com/ or http://screenshots.debian.org/(they're >>>> the same website anyway). >>>> >>>> As for paid apps, there's a staggering number of possibilities. Ideally >>>> we'd use something distribution- and vendor-independent, and I have a few >>>> ideas on how to achieve that. But IMO it's too early to discuss >>>> implementing paid apps yet. We'll design the architecture for that when we >>>> get there. >>>> >>>> -- >>>> Sergey "Shnatsel" Davidoff >>>> OS architect @ elementary >>> >>> >> >> -- >> Mailing list: https://launchpad.net/~elementary-dev-community >> Post to : elementary-dev-community@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~elementary-dev-community >> More help : https://help.launchpad.net/ListHelp >> >> > > > -- > *------------------------------**------------------------------** > Chris Timberlake* > Technical Architect > Phone: 515-707-5109 > gam...@gmail.com > > -- > Mailing list: https://launchpad.net/~elementary-dev-community > Post to : elementary-dev-community@lists.launchpad.net > Unsubscribe : https://launchpad.net/~elementary-dev-community > More help : https://help.launchpad.net/ListHelp > >
-- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
