https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • v
    the repos will remain at their current locations, but will they continue to be updated or will they be left to bitrot?
  • d
    no we will only be building the EULA based packages
  • v
    David: so if they are private forks, how can we verify the bits are in there don't contain backdoors?
  • v
    So how do I run OSS puppet without paying?
  • d
    changes on our side will be made to the private repos then pushed upstream to the publics
  • v
    my hope was that the community or a collective of companies build opensource packages and PE will reuse them while perforce sponsors the development of those packages
  • v
    but then why do you have the fork at all
  • d
    there are discussions of how we can support vox to build packages
  • v
    will we be able to send bug reports and patches... somewhere?
  • v
    wrong question. correct is: will finally people responds to our patches in a meaningful time?
  • v
    that too heh, I guess I'm biased because most of my patches have actually gone in (to my surprise)
  • v
    everything related to PE is incredible hard to get in / get a response at all / figure out who is responsible
  • d
    This would be ideal to raise at EAB and townhall. I would like to do a full review of our public repos, ensure we have a contribution statement on them, a triage cycle and clear team ownership
  • d
    similar to how DevX are handling their repos currently
  • v
    yeah DevX does a great job
  • v
    my main concern is that the delay in pushing to public repos will make contributing harder and also harder to merge, since we can't rebase on current code to help.
  • v
    also it sounds like a distro maintainer will not get security fixes until 1day.
  • v
    i find this announcement to be confusing and alarming
  • v
    what are in the EULA repos?
  • v
    is perforce effectively forking puppet into a proprietary version, where changes will be available back to the community only after a while?
  • v
    how will security issues be handled?
  • v
    I'm concerned that the recent moves are just precursors to more dismantling of the free software community around the software
    this 3
  • v
    I would prefer it if the open repos are the actual upstream ones, not the other way around
    1000 6
  • v
    it's really frustrating how perforce is proceeding here, first with the cavalier approach with the slack channels, which was kind of rolled back but only after uproar, then this
  • v
    why can't we have a frank conversation about this?
  • v
    you want to close source puppet, fine, just freaking do it and be done with it
  • v
    don't mess around pretending this is for "hardening" or security
  • v
    shit or get off the pot, if you pardon my french
    💯 1
  • v
    then we'll deal with the crap, as we always do
  • d
    There is not intention to close source, we will be having follow ups in Townhall webinars and EAB to find how best to make this work for all and where we can provide support
1...617618619...648Latest