Hey all,
Having been around for a few years I've inherited or added quite a few
pkgs to the tree that I wouldn't mind other people fixing/bumping/etc
that don't fall into any current herds.
With that in mind, I think it would be an interesting experiment if we
had a collaborative herd (probably n
On 13:22 Mon 23 Mar , Tim Harder wrote:
> Hey all,
Hi,
> ...
> With that in mind, I think it would be an interesting experiment if we
> had a collaborative herd (probably named "collab") that signals the
> status that anyone is generally free to fix, bump, or do sane things to
> the pkgs with
On 2015-03-23 13:48, Panagiotis Christopoulos wrote:
> You want to have a herd for that or something in metadata.xml that would
> raise a
> flag that the package can be freely touched/maintained by anyone?
I'd rather have a herd so people can easily scan via euscan or similar to see
the entire ar
On Mon, 23 Mar 2015 14:49:44 -0400 Tim Harder wrote:
> On 2015-03-23 13:48, Panagiotis Christopoulos wrote:
> > You want to have a herd for that or something in metadata.xml that would
> > raise a
> > flag that the package can be freely touched/maintained by anyone?
>
> I'd rather have a herd so
On Mon, 23 Mar 2015 22:53:45 +0300
Andrew Savchenko wrote:
> On Mon, 23 Mar 2015 14:49:44 -0400 Tim Harder wrote:
> > On 2015-03-23 13:48, Panagiotis Christopoulos wrote:
> > > You want to have a herd for that or something in metadata.xml
> > > that would raise a flag that the package can be free
El lun, 23-03-2015 a las 13:22 -0400, Tim Harder escribió:
> Hey all,
>
> Having been around for a few years I've inherited or added quite a few
> pkgs to the tree that I wouldn't mind other people fixing/bumping/etc
> that don't fall into any current herds.
>
> With that in mind, I think it woul
On 2015-03-23 18:54, Pacho Ramos wrote:
> Personally I think a tag in metadata to show that a package can be
> touched by others freely would be much more useful than having a big
> herd with a mix of packages that are not even related.
Sure, I'd just like to expose this status in a better manner
On Monday, March 23, 2015 01:22:25 PM Tim Harder wrote:
> Hey all,
>
> Having been around for a few years I've inherited or added quite a few
> pkgs to the tree that I wouldn't mind other people fixing/bumping/etc
> that don't fall into any current herds.
>
> With that in mind, I think it would b
On 03/23/2015 01:22 PM, Tim Harder wrote:
> Hey all,
>
> Having been around for a few years I've inherited or added quite a few
> pkgs to the tree that I wouldn't mind other people fixing/bumping/etc
> that don't fall into any current herds.
>
> With that in mind, I think it would be an interesti
On Mon, 23 Mar 2015 13:22:25 -0400
Tim Harder wrote:
> Hey all,
>
> Having been around for a few years I've inherited or added quite a few
> pkgs to the tree that I wouldn't mind other people fixing/bumping/etc
> that don't fall into any current herds.
>
> With that in mind, I think it would be
Dnia 2015-03-23, o godz. 13:22:25
Tim Harder napisał(a):
> Having been around for a few years I've inherited or added quite a few
> pkgs to the tree that I wouldn't mind other people fixing/bumping/etc
> that don't fall into any current herds.
>
> With that in mind, I think it would be an intere
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23/03/15 01:22 PM, Tim Harder wrote:
> Hey all,
>
> Having been around for a few years I've inherited or added quite a
> few pkgs to the tree that I wouldn't mind other people
> fixing/bumping/etc that don't fall into any current herds.
>
> With
On Tue, Mar 24, 2015 at 08:41:52AM +0100, Alexis Ballier wrote:
> On Mon, 23 Mar 2015 13:22:25 -0400
> Tim Harder wrote:
>
> > Hey all,
> >
> > Having been around for a few years I've inherited or added quite a few
> > pkgs to the tree that I wouldn't mind other people fixing/bumping/etc
> > tha
On 23.03.2015 18:22, Tim Harder wrote:
> With that in mind, I think it would be an interesting experiment if
> we had a collaborative herd (probably named "collab") that signals
> the status that anyone is generally free to fix, bump, or do sane
> things to the pkgs with the caveat that you fix wha
El mié, 25-03-2015 a las 21:25 +, Robin H. Johnson escribió:
[...]
> - timeout:
> this is how long you we suggest you wait for the maintainer/team to
> comment on your change.
> Format should be a short duration specifier per ISO8601
> I'd like to default it to 1 week: 'P1W'.
[...]
I w
On Fri, Mar 27, 2015 at 09:45:25PM +0100, Pacho Ramos wrote:
> El mié, 25-03-2015 a las 21:25 +, Robin H. Johnson escribió:
> [...]
> > - timeout:
> > this is how long you we suggest you wait for the maintainer/team to
> > comment on your change.
> > Format should be a short duration spec
El vie, 27-03-2015 a las 21:03 +, Robin H. Johnson escribió:
> On Fri, Mar 27, 2015 at 09:45:25PM +0100, Pacho Ramos wrote:
> > El mié, 25-03-2015 a las 21:25 +, Robin H. Johnson escribió:
> > [...]
> > > - timeout:
> > > this is how long you we suggest you wait for the maintainer/team to
On Fri, 27 Mar 2015 22:14:04 +0100
Pacho Ramos wrote:
> I would prefer 1M (well... if the developer is not able to even
> comment in bug reports in 1 month, maybe he should have at least a
> devaway message explaining how to deal with his/her packages if he is
> not able to reply so "soon") :/
>
18 matches
Mail list logo
