Re: [OpenWrt-Devel] openwrt and lede - remerge proposal
On 05/08/2017 06:19 AM, John Crispin wrote: > Hi, > > Felix, Imre and myself had 2 calls last week lasting several hours and > discussed the following proposal of conditions for a remerge that we > would like to propose and have people vote on. > > *) branding > - the owrt side sees no option of using the lede brand > > - a (minor) majority voted for openwrt as a name over lede whilst most > people said they did not care > > - as the last vote had a 100% ACK for a remerge using the owrt brand is > the only feasible option > > *) domain > - transfer owner ship to SPI for openwrt.org and lede-project.org > - add them to the pool of urls at digital ocean > - post remerge build a setup where we have several DNS servers in > various locations > - point git.openwrt.org at the lede git server > - point bugs.openwrt.org to the lede flyspray instance > - keep both wikis and forums as is (we should decide post remerge how to > proceed to avoid these issues blocking the progress) > - update the lede domain entries for build/download/rsync/... servers so > that the openwrt domain also points at them > > *) SPI > - TBD post remerge > > *) github > - stop pushing to lede-project organisation > - start pushing to the openwrt organisation > - cleanup the list of owners in the openwrt organisation > - obsolete all issues on the openwrt organisation and close the issue > tracker > - go through the open openwrt and lede PRs, pickup whats useful and > close the rest, asking people to repost (things wont be rebasable anyhow) > - close the lede PR tracker > - keep the lede organisation in its current state so that forked trees > dont get obsoleted > > - obsolete the lede github org after a grace period of 3-6 months > > *) landing page > - update the lede landing page to represent the openwrt name > - update the landing page to have the same look & feel as the current > openwrt landing page > - point openwrt.org at the lede landing page > > *) trac > - trac is already readonly, keep content so that search engines can > still find the it > - edit the trac html templates, adding a note pointing at the > bug.openwrt.org instance > > *) email accounts > - currently there are around ~20 active openwrt.org mail accounts > - turn all the webmaster@, hostmaster@, ... accounts into aliases that > anyone with voting rights can be subscribed to > - ask those people that are no longer active to voluntarily give up > their accounts > - mail addresses may under no conditions be used for any personal > business, consultancy, applying for jobs, ... purposes > > - any mail sent from an openwrt.org account needs to adhere the > trademark policy and should only be used for FOSS purposes > > > *) wiki / forum > - TBD > - asking in either forum/wiki will get a biased vote so keep them both > around > - start a separate discussion regarding these post remerge > > *) LF > - find out what doubts folks have about LF > - find out benefits - we would have their hosting and sponsorship ?! > - start a separate discussion regarding these post remerge > > *) git trees > - rebrand the lede tree to openwrt > - work out what has happened inside the openwrt tree since the reboot > and pick up the useful bits (zoltan has done some prior work on this > already) > > *) mailing list > - ask david to add the openwrt-adm and openwrt lists > - announce the switch to the infradead serves, asking people to > unsubscribe if they have privacy issues with this > - import the user DB from the current openwrt and lede ML into the 2 new > mailing lists > - find out if we can redirect/auto-reply the existing lists to the new > ones > > *) trademark/sponsorship policy > - review/ack imres trademark policy > - review/ack jows sponsorship policy > > *) timeline > - refine / vote / agree on the proposal withing the next 2 week > - work on the action items in the 4 weeks after that All of this sounds good me, and thanks for taking the time to talk to each other and come to an agreement. How can we help? -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [LEDE-DEV] openwrt and lede - remerge proposal
On 2017-05-09 18:29, Philip Prindeville wrote: > I’d like to suggest one more action item to this list if I can. It > would be handy to have a single database for user > authentication/identification for submitting bugs, editing the Wiki, etc. > > Previously there were too many places where you had to create an > account. If we can’t do “single sign-on”, can we at least do “single > sign-up”? > > And part of a user’s profile should include their IRC handle > (assuming they have one). The todo list for the merge is already quite long, and we need to avoid any unnecessary delay in getting it done. Stuff like this will have to wait... - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [LEDE-DEV] openwrt and lede - remerge proposal
> On May 8, 2017, at 7:19 AM, John Crispin wrote: > > Hi, > > Felix, Imre and myself had 2 calls last week lasting several hours and > discussed the following proposal of conditions for a remerge that we would > like to propose and have people vote on. > > *) branding > - the owrt side sees no option of using the lede brand > > - a (minor) majority voted for openwrt as a name over lede whilst most people > said they did not care > > - as the last vote had a 100% ACK for a remerge using the owrt brand is the > only feasible option > > *) domain > - transfer owner ship to SPI for openwrt.org and lede-project.org > - add them to the pool of urls at digital ocean > - post remerge build a setup where we have several DNS servers in various > locations > - point git.openwrt.org at the lede git server > - point bugs.openwrt.org to the lede flyspray instance > - keep both wikis and forums as is (we should decide post remerge how to > proceed to avoid these issues blocking the progress) > - update the lede domain entries for build/download/rsync/... servers so that > the openwrt domain also points at them > > *) SPI > - TBD post remerge > > *) github > - stop pushing to lede-project organisation > - start pushing to the openwrt organisation > - cleanup the list of owners in the openwrt organisation > - obsolete all issues on the openwrt organisation and close the issue tracker > - go through the open openwrt and lede PRs, pickup whats useful and close the > rest, asking people to repost (things wont be rebasable anyhow) > - close the lede PR tracker > - keep the lede organisation in its current state so that forked trees dont > get obsoleted > > - obsolete the lede github org after a grace period of 3-6 months > > *) landing page > - update the lede landing page to represent the openwrt name > - update the landing page to have the same look & feel as the current openwrt > landing page > - point openwrt.org at the lede landing page > > *) trac > - trac is already readonly, keep content so that search engines can still > find the it > - edit the trac html templates, adding a note pointing at the bug.openwrt.org > instance > > *) email accounts > - currently there are around ~20 active openwrt.org mail accounts > - turn all the webmaster@, hostmaster@, ... accounts into aliases that anyone > with voting rights can be subscribed to > - ask those people that are no longer active to voluntarily give up their > accounts > - mail addresses may under no conditions be used for any personal business, > consultancy, applying for jobs, ... purposes > > - any mail sent from an openwrt.org account needs to adhere the trademark > policy and should only be used for FOSS purposes > > > *) wiki / forum > - TBD > - asking in either forum/wiki will get a biased vote so keep them both around > - start a separate discussion regarding these post remerge > > *) LF > - find out what doubts folks have about LF > - find out benefits - we would have their hosting and sponsorship ?! > - start a separate discussion regarding these post remerge > > *) git trees > - rebrand the lede tree to openwrt > - work out what has happened inside the openwrt tree since the reboot and > pick up the useful bits (zoltan has done some prior work on this already) > > *) mailing list > - ask david to add the openwrt-adm and openwrt lists > - announce the switch to the infradead serves, asking people to unsubscribe > if they have privacy issues with this > - import the user DB from the current openwrt and lede ML into the 2 new > mailing lists > - find out if we can redirect/auto-reply the existing lists to the new ones > > *) trademark/sponsorship policy > - review/ack imres trademark policy > - review/ack jows sponsorship policy > > *) timeline > - refine / vote / agree on the proposal withing the next 2 week > - work on the action items in the 4 weeks after that > >John I’d like to suggest one more action item to this list if I can. It would be handy to have a single database for user authentication/identification for submitting bugs, editing the Wiki, etc. Previously there were too many places where you had to create an account. If we can’t do “single sign-on”, can we at least do “single sign-up”? And part of a user’s profile should include their IRC handle (assuming they have one). Thanks. -Philip ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [LEDE-DEV] openwrt and lede - remerge proposal
> On May 8, 2017, at 7:29 AM, David Woodhouse wrote: > > On Mon, 2017-05-08 at 15:19 +0200, John Crispin wrote: >> >> *) mailing list >> - ask david to add the openwrt-adm and openwrt lists >> - announce the switch to the infradead serves, asking people to >> unsubscribe if they have privacy issues with this >> - import the user DB from the current openwrt and lede ML into the 2 new >> mailing lists >> - find out if we can redirect/auto-reply the existing lists to the new ones > > Yes, we can redirect the existing lists to the new ones — so for > example, mail sent to lede-dev will just turn up on the openwrt-dev > list instead. Assuming that's what you meant. > > For importing subscribers, if that's what you want to do, I'd be > inclined to send *invitations* not just subscribe people. So each > person will get the 'someone has requested that your address be > subscribed; click here to actually do it' message. We can write our own > blurb to go out at the top of those invitations. I think that would be better. I whitelist all of my mailing list subscriptions, so the reminder that I need to add a new one (when I’m not actually subscribing myself) is always helpful. -Philip ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Factory startup issues since mount_root / libfstools improvements in Chaos Calmer
Hi Rafał,
On 09 May 2017 at 10:25, Rafał Miłecki wrote:
> On 8 May 2017 at 13:43, Smith, Pieter wrote:
> > I am still hoping to get confirmation from you on this patch. Is this
> > acceptable for upstreaming?
> >
> >> Hi Rafał,
> >>
> >> > > On 03/29/2017 11:53 AM, Smith, Pieter wrote:
> >> > > > My apologies. I am not able to get mutt working with our
> >> > > > corporate infrastructure. I hope it arrives unmangled as an
> >> > > > attachment. If not, I'll use my personal mail.
> >> > >
> >> > > This would be acceptable for me to pick patch sent as attachment,
> >> > > but you really need to sign it off with your name. Please add a
> >> > > proper
> >> > > Signed-off-by:
> >> > > line and resend.
> >> >
> >> > Off-course! My bad...
> >>
> >> In adding more logging so that you can diagnose the issue, I tracked down
> >> the root cause and fixed the issue. Attached, > > please find an updated
> >> patch with sign-off and a problem description.
>
> Sorry, it took me more time than it was supposed to. Your patch went into the
> fstools repository.
>
> 1) LEDE master branch
> We'll bump package after fixing regression caused by commit
> a19f2b3c21288 ("build: disable the format-truncation warning error to fix gcc
> 7 build errors") which results in:
> cc1: error: -Werror=format-truncation: no option -Wformat-truncation
>
> 2) LEDE lede-17.01 branch:
> I sent patch to backport your fix:
> https://patchwork.ozlabs.org/patch/759957/
>
> 3) OpenWrt 15.05 branch:
> I don't really want to mess with that. I don't know if I have privileges nor
> if my patch could be accepted. We need someone > working on OpenWrt to handle
> this.
>
> --
> Rafał
Thanks for the confirmation!
- Pieter
The information contained in this message may be confidential and legally
protected under applicable law. The message is intended solely for the
addressee(s). If you are not the intended recipient, you are hereby notified
that any use, forwarding, dissemination, or reproduction of this message is
strictly prohibited and may be unlawful. If you are not the intended recipient,
please contact the sender by return e-mail and destroy all copies of the
original message.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Factory startup issues since mount_root / libfstools improvements in Chaos Calmer
On 8 May 2017 at 13:43, Smith, Pieter wrote:
> I am still hoping to get confirmation from you on this patch. Is this
> acceptable for upstreaming?
>
>> Hi Rafał,
>>
>> > > On 03/29/2017 11:53 AM, Smith, Pieter wrote:
>> > > > My apologies. I am not able to get mutt working with our corporate
>> > > > infrastructure. I hope it arrives unmangled as an attachment. If
>> > > > not, I'll use my personal mail.
>> > >
>> > > This would be acceptable for me to pick patch sent as attachment,
>> > > but you really need to sign it off with your name. Please add a
>> > > proper
>> > > Signed-off-by:
>> > > line and resend.
>> >
>> > Off-course! My bad...
>>
>> In adding more logging so that you can diagnose the issue, I tracked down
>> the root cause and fixed the issue. Attached, > please find an updated patch
>> with sign-off and a problem description.
Sorry, it took me more time than it was supposed to. Your patch went
into the fstools repository.
1) LEDE master branch
We'll bump package after fixing regression caused by commit
a19f2b3c21288 ("build: disable the format-truncation warning error to
fix gcc 7 build errors") which results in:
cc1: error: -Werror=format-truncation: no option -Wformat-truncation
2) LEDE lede-17.01 branch:
I sent patch to backport your fix:
https://patchwork.ozlabs.org/patch/759957/
3) OpenWrt 15.05 branch:
I don't really want to mess with that. I don't know if I have
privileges nor if my patch could be accepted. We need someone working
on OpenWrt to handle this.
--
Rafał
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] openwrt and lede - remerge proposal
On Tue, May 9, 2017 at 9:50 AM, John Crispin wrote: > > > On 09/05/17 09:49, Rafał Miłecki wrote: >> >> On 8 May 2017 at 15:19, John Crispin wrote: >>> >>> *) domain >>> - transfer owner ship to SPI for openwrt.org and lede-project.org >>> (...) >>> >>> *) SPI >>> - TBD post remerge >> >> This is unclear to me. Are we postponing setting rules with SPI on how >> they should manage domains? I guess it should be handled at the same >> time: specifying rules (majority of votes?) and handling domains. > > SPi will need a new liaison officer (team). we need to vote on who this will > be. apart from that SPI will be pointed at the wiki page listing voters and > rules. domains will be handed over to them SPI offers different services to projects like accepting donations and holding funds, legal assistance, technical services, etc ... Apart from handing over the domains do we want to make use of any of the services offered by SPI ? Further nice to read we convergence again; thx for the effort ! Hans > > John > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] openwrt and lede - remerge proposal
On 9 May 2017 at 09:50, John Crispin wrote: > On 09/05/17 09:49, Rafał Miłecki wrote: >> >> On 8 May 2017 at 15:19, John Crispin wrote: >>> >>> *) domain >>> - transfer owner ship to SPI for openwrt.org and lede-project.org >>> (...) >>> >>> *) SPI >>> - TBD post remerge >> >> This is unclear to me. Are we postponing setting rules with SPI on how >> they should manage domains? I guess it should be handled at the same >> time: specifying rules (majority of votes?) and handling domains. > > SPi will need a new liaison officer (team). we need to vote on who this will > be. apart from that SPI will be pointed at the wiki page listing voters and > rules. domains will be handed over to them Sounds OK, we probably should just handle this at the same time as handling the domains. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] openwrt and lede - remerge proposal
On 09/05/17 09:49, Rafał Miłecki wrote: On 8 May 2017 at 15:19, John Crispin wrote: *) domain - transfer owner ship to SPI for openwrt.org and lede-project.org (...) *) SPI - TBD post remerge This is unclear to me. Are we postponing setting rules with SPI on how they should manage domains? I guess it should be handled at the same time: specifying rules (majority of votes?) and handling domains. SPi will need a new liaison officer (team). we need to vote on who this will be. apart from that SPI will be pointed at the wiki page listing voters and rules. domains will be handed over to them John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] openwrt and lede - remerge proposal
On 8 May 2017 at 15:19, John Crispin wrote: > *) domain > - transfer owner ship to SPI for openwrt.org and lede-project.org > (...) > > *) SPI > - TBD post remerge This is unclear to me. Are we postponing setting rules with SPI on how they should manage domains? I guess it should be handled at the same time: specifying rules (majority of votes?) and handling domains. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
