On Wed, Mar 29, 2023 at 8:43 AM Alessandro Lai <alessandro.la...@gmail.com> wrote:
> Hello everyone, > I would like to revive the discussion here. I've done all the changes on > the PR, and the issues on the mailing list seems to be gone. There were a > couple of deleted messages in this thread, so please chime back in if your > position is not clear here. > > If no one objects or has further suggestions, I would like to put this to > a vote in a short time, to avoid going against the election period, which > would be in May. > I've left a review. I think the first few sections need to be simplified tremendously. On a first read, the first few sections feel very contradictory, and it takes a few reads to understand the intent. It needs to be simplified so that those reading can understand immediately what the intent is, and how the by-law is structured to get there. Thanks. > > Il giorno lunedì 6 marzo 2023 alle 12:35:01 UTC+1 Alessandro Lai ha > scritto: > >> I should report back what was said on Discord about this matter. >> >> I said that handing over our money problems to a single sponsor puts us >> in a bad position, because: >> - we should avoid handling money personally (secretaries shouldn't have >> financial/fiscal impact due to money going around) >> - previous point could be handled with the sponsor paying directly, but >> that's not always feasible.. we can't give them access to all the needed >> accounts! (i.e. the NameCheap one) >> - the sponsor could drop us at any time, unannounced, especially when a >> payment is due, which brings us back to square one >> >> Korvin then voiced opposition against collecting money, or more >> specifically against asking for donation; I can understand this, and I >> would then prefer to struck down any piece of the bylaw that endorse this. >> I'm open to even deny that, so that our only source of money are >> organization like TideLift, that collect money from private, for-profit >> entities, so that we can sustain ourselves, pay for more stuff (like >> trademarking our name) and that's all. >> >> Korvin, would this resolve your doubts? >> >> PS: we received money on Thanks.dev from Sentry today :-/ we need to sort >> this out! >> >> Il giorno lunedì 27 febbraio 2023 alle 07:31:28 UTC+1 korvin...@gmail.com >> ha scritto: >> >>> I understand that our expenses are under $100/yr total, Concrete CMS >>> would be happy to cover that cost moving forward! >>> >>> I don't really get how asking for donations contributes to our mission >>> as an organization. Can you speak how it does and to what you intend to >>> spend extra funds on specifically? To me this sounds against the spirit of >>> our organization and feels like a big mistake. >>> >>> Thanks, >>> Korvin >>> >>> On Sat, Feb 25, 2023, 5:05 AM Tim Düsterhus <t...@bastelstu.be> wrote: >>> >>>> Hi >>>> >>>> On 2/24/23 00:03, Alessandro Lai wrote: >>>> > I had the idea of proposing a "funding" bylaw for quite some time, >>>> > especially because, as a secretary, I had to see the domains or the >>>> email >>>> > account nearly expire multiple times during this year, and finding a >>>> > permanent solution to that issue is something that I want. >>>> > >>>> >>>> Regarding the domain expiry I can recommend choosing a registrar that >>>> supports multi-year registrations to avoid the hassle of renewing >>>> domains on short notice (and possibly forgetting entirely). >>>> >>>> All my important personal domains and all $dayjob domains using a TLD >>>> that supports multi-year registrations are registered for the next five >>>> years or so *and* are yearly topped up by another year. That way >>>> there's >>>> always a 5-year headroom if something goes wrong (e.g. the registrar >>>> going out of business). >>>> >>>> In fact it appears that the current registrar "Namecheap" does support >>>> multi-year registrations: >>>> >>>> https://www.namecheap.com/support/knowledgebase/article.aspx/770/35/is-it-possible-to-registerrenew-a-domain-name-for-more-than-10-years/ >>>> >>>> Best regards >>>> Tim Düsterhus >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "PHP Framework Interoperability Group" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to php-fig+u...@googlegroups.com. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/php-fig/3ab0d950-32f7-75c7-fd19-5e691676f8be%40bastelstu.be >>>> . >>>> >>> -- > You received this message because you are subscribed to the Google Groups > "PHP Framework Interoperability Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to php-fig+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/php-fig/24143cea-6a78-4b1e-84b9-a372c84b9a69n%40googlegroups.com > <https://groups.google.com/d/msgid/php-fig/24143cea-6a78-4b1e-84b9-a372c84b9a69n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Matthew Weier O'Phinney mweierophin...@gmail.com https://mwop.net/ he/him -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAJp_myUgxVQPq%2BF8M9mSLOB4N9tt1qj0fQF_Piyv7X6E2ibgPw%40mail.gmail.com.
