Re: [Elementary-dev-community] What it takes to be a dev

2011-11-19 Thread Daniel Foré 
As far as packaging goes, I think it's unrealistic to expect that we'll always 
be able to package every third party app that comes along. It's just not a 
scalable practice. I do think it's worth trying to shift the responsibility of 
providing a complete product (a packaged product) to the developer and not the 
platform.

Best Regards,
Daniel Foré

www.elementaryos.org

On Nov 19, 2011, at 9:14 PM, Avi Romanoff  wrote:

> While I don't disagree with that, I think it's something we're trying to move 
> away from.
> 
> I could be wrong, but I think that for elementary to thrive as a platform for 
> third-party developers, we're going to automate packaging fully. (Maybe not 
> for libraries, but certainly for apps).
> 
> Granted, this is probably completely moot since none of that technology 
> exists. I guess I just wanted us to not get *too* carried away about 
> packaging (and this is probably in agreement with what Christian and Serge 
> are saying) and not spend a great deal of time if any discussing it in 
> documentation.
> 
> Just my $0.02.
> 
> On Sat, Nov 19, 2011 at 2:21 PM, Christian Dywan  
> wrote:
> Am 19.11.2011 09:22, schrieb Сергей:
> 
> Regarding daily builds: they require existing Debian packaging, and I
> don't think it's a good idea to make the developer package their app,
> too.
> Division of labor produces better results, and since I don't have a
> monopoly for Debian packaging in elementary anymore (Mario Guerriero
> and Cody Garver package stuff very well), packaging shouldn't be a
> bottleneck.
> I heavily second that. I've said it more than once. It is very rare for 
> developers to package their own software. If a package is any good, packagers 
> take care of it. Packagers have the benefit of more experience, routine and 
> finding additional bugs. And it takes away development time.
> 
> 
> -- 
> 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
-- 
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

Re: [Elementary-dev-community] What it takes to be a dev

2011-11-19 Thread Avi Romanoff 
While I don't disagree with that, I think it's something we're trying to
move away from.

I could be wrong, but I think that for elementary to thrive as a platform
for third-party developers, we're going to automate packaging fully. (Maybe
not for libraries, but certainly for apps).

Granted, this is probably completely moot since none of that technology
exists. I guess I just wanted us to not get *too* carried away about
packaging (and this is probably in agreement with what Christian and Serge
are saying) and not spend a great deal of time if any discussing it in
documentation.

Just my $0.02.

On Sat, Nov 19, 2011 at 2:21 PM, Christian Dywan wrote:

> Am 19.11.2011 09:22, schrieb Сергей:
>
>  Regarding daily builds: they require existing Debian packaging, and I
>> don't think it's a good idea to make the developer package their app,
>> too.
>> Division of labor produces better results, and since I don't have a
>> monopoly for Debian packaging in elementary anymore (Mario Guerriero
>> and Cody Garver package stuff very well), packaging shouldn't be a
>> bottleneck.
>>
> I heavily second that. I've said it more than once. It is very rare for
> developers to package their own software. If a package is any good,
> packagers take care of it. Packagers have the benefit of more experience,
> routine and finding additional bugs. And it takes away development time.
>
>
> --
> 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

Re: [Elementary-dev-community] What it takes to be a dev

2011-11-19 Thread Christian Dywan 

Am 19.11.2011 09:22, schrieb Сергей:

Regarding daily builds: they require existing Debian packaging, and I
don't think it's a good idea to make the developer package their app,
too.
Division of labor produces better results, and since I don't have a
monopoly for Debian packaging in elementary anymore (Mario Guerriero
and Cody Garver package stuff very well), packaging shouldn't be a
bottleneck.
I heavily second that. I've said it more than once. It is very rare for 
developers to package their own software. If a package is any good, 
packagers take care of it. Packagers have the benefit of more 
experience, routine and finding additional bugs. And it takes away 
development time.


--
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

Re: [Elementary-dev-community] What it takes to be a dev

2011-11-19 Thread Сергей 
Regarding daily builds: they require existing Debian packaging, and I
don't think it's a good idea to make the developer package their app,
too.
Division of labor produces better results, and since I don't have a
monopoly for Debian packaging in elementary anymore (Mario Guerriero
and Cody Garver package stuff very well), packaging shouldn't be a
bottleneck.

-- 
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

Re: [Elementary-dev-community] What it takes to be a dev

2011-11-19 Thread Сергей 
We have http://elementaryos.org/docs/developer-guide in progress for like
ages.

Pages that still need work:
http://elementaryos.org/docs/developer-guide/introduction/elementary-developer-sdk
http://elementaryos.org/docs/developer-guide/hello-world/revision-control
http://elementaryos.org/docs/developer-guide/hello-world/setting-translations
http://elementaryos.org/docs/developer-guide/hello-world/nightly-builds -
do we need it at all?
http://elementaryos.org/docs/first-steps - it would be better to store the
modules somewhere else than in UbuntuOne, people get 503 with it far too
often
http://elementaryos.org/docs/developer-guide/cmake/installation

Also, I think we need to restructure the page, maybe slit basic features
and advanced setup... I'm not sure if we should scare people away with
translation support woes right away. And info about submitting code seems
scattered right now.

Regarding low traffic in this list: there are too few people in here for a
decent amount of traffic. The team should be owned by ~elementary-core, and
we should get more devs subscribed.

--
Sergey "Shnatsel" Davidoff
-- 
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