No need to apologize! Perhaps this confusion shows that the current process surrounding creating/modifying/drafting BOLT documents does indeed need to be better documented. We've more or less been rolling along with a pretty minimal process among the various implementations which I'd say has worked pretty well so far. However as more contributors get involved we may need to add a bit more structure to ensure things are transparent for newcomers.
On Sun, Jul 22, 2018, 12:57 PM René Pickhardt <r.pickha...@googlemail.com> wrote: > Sorry did not realized that BOLTs are the equivalent - and aparently many > people I spoke to also didn't realize that. > > I thought BOLT is the protocol specification and the bolts are just the > sections. And the BOLT should be updated to a new version. > > Also I suggested that this should take place for example within the > lightning rfc repo. So my suggestion was not about creating another place > but more about making the process more transparent or kind of filling the > gap that I felt was there. > > I am sorry for spaming mailboxes with my suggestion just because I didn't > understand the current process. > > > Olaoluwa Osuntokun <laol...@gmail.com> schrieb am So., 22. Juli 2018 > 20:59: > >> We already have the equiv of improvement proposals: BOLTs. Historically >> new standardization documents are proposed initially as issues or PR's when >> ultimately accepted. Why do we need another repo? >> >> On Sun, Jul 22, 2018, 6:45 AM René Pickhardt via Lightning-dev < >> lightning-dev@lists.linuxfoundation.org> wrote: >> >>> Hey everyone, >>> >>> in the grand tradition of BIPs I propose that we also start to have our >>> own LIPs (Lightning Network Improvement proposals) >>> >>> I think they should be placed on the github.com/lightning account in a >>> repo called lips (or within the lightning rfc repo) until that will happen >>> I created a draft for LIP-0001 (which is describing the process and is 95% >>> influenced by BIP-0002) in my github repo: >>> >>> https://github.com/renepickhardt/lips (There are some open Todos and >>> Questions in this LIP) >>> >>> The background for this Idea: I just came home from the bitcoin munich >>> meetup where I held a talk examining BOLT. As I was asked to also talk >>> about the future plans of the developers for BOLT 1.1 I realized while >>> preparing the talk that many ideas are distributed within the community but >>> it seems we don't have a central place where we collect future enhancements >>> for BOLT1.1. Having this in mind I think also for the meeting in Australia >>> it would be nice if already a list of LIPs would be in place so that the >>> discussion can be more focused. >>> potential LIPs could include: >>> * Watchtowers >>> * Autopilot >>> * AMP >>> * Splicing >>> * Routing Protcols >>> * Broadcasting past Routing statistics >>> * eltoo >>> * ... >>> >>> As said before I would volunteer to work on a LIP for Splicing (actually >>> I already started) >>> >>> best Rene >>> >>> >>> -- >>> https://www.rene-pickhardt.de >>> >>> Skype: rene.pickhardt >>> >>> mobile: +49 (0)176 5762 3618 >>> _______________________________________________ >>> Lightning-dev mailing list >>> Lightning-dev@lists.linuxfoundation.org >>> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev >>> >> > Am 22.07.2018 20:59 schrieb "Olaoluwa Osuntokun" <laol...@gmail.com>: > > We already have the equiv of improvement proposals: BOLTs. Historically > new standardization documents are proposed initially as issues or PR's when > ultimately accepted. Why do we need another repo? > > On Sun, Jul 22, 2018, 6:45 AM René Pickhardt via Lightning-dev < > lightning-dev@lists.linuxfoundation.org> wrote: > >> Hey everyone, >> >> in the grand tradition of BIPs I propose that we also start to have our >> own LIPs (Lightning Network Improvement proposals) >> >> I think they should be placed on the github.com/lightning account in a >> repo called lips (or within the lightning rfc repo) until that will happen >> I created a draft for LIP-0001 (which is describing the process and is 95% >> influenced by BIP-0002) in my github repo: >> >> https://github.com/renepickhardt/lips (There are some open Todos and >> Questions in this LIP) >> >> The background for this Idea: I just came home from the bitcoin munich >> meetup where I held a talk examining BOLT. As I was asked to also talk >> about the future plans of the developers for BOLT 1.1 I realized while >> preparing the talk that many ideas are distributed within the community but >> it seems we don't have a central place where we collect future enhancements >> for BOLT1.1. Having this in mind I think also for the meeting in Australia >> it would be nice if already a list of LIPs would be in place so that the >> discussion can be more focused. >> potential LIPs could include: >> * Watchtowers >> * Autopilot >> * AMP >> * Splicing >> * Routing Protcols >> * Broadcasting past Routing statistics >> * eltoo >> * ... >> >> As said before I would volunteer to work on a LIP for Splicing (actually >> I already started) >> >> best Rene >> >> >> -- >> https://www.rene-pickhardt.de >> >> Skype: rene.pickhardt >> >> mobile: +49 (0)176 5762 3618 >> _______________________________________________ >> Lightning-dev mailing list >> Lightning-dev@lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev >> > >
_______________________________________________ Lightning-dev mailing list Lightning-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
