Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Sam Ruby
Agile Web Development with Rails 7.2
Rails 7.2 completely redefined what it means to produce fantastic user experiences and provides a way to achieve all the benefits of single-page applications—at a fraction of the complexity. Rails 7.2 integrated the Hotwire frameworks of Stimulus and Turbo directly as the new defaults, together with that hot newness of import maps. The result is a toolkit so powerful that it allows a single individual to create modern applications upon which they can build a competitive business.
Agile Web Development with Rails 7
Book description Rails 7 completely redefines what it means to produce fantastic user experiences and provides a way to achieve all the benefits of single-page applications - at a fraction of the complexity. Rails 7 integrates the Hotwire frameworks of Stimulus and Turbo directly as the new defaults, together with that hot newness of import maps. The result is a toolkit so powerful that it allows a single individual to create modern applications upon which they can build a competitive business.
Position Paper
This version contains edits not present in the version sent to the White House Executive Summary / Key Take-Aways We can't fix open source supply chain issues by focusing exclusively on the upstream producer Even perfect releases can take years to be adopted and deployed by downstream providers. Community is defined by those who show up and do the work Companies that build open source into their products rarely participate in their continued maintenance.
[DISCUSS] IPMC votes on releases)
On Wed, Aug 14, 2019 at 9:47 PM Justin Mclean <justin@classsoftware.com> wrote: > > Hi > > Thanks for the idea and offer of help. > > > 1) Concurrent with the start of a release vote by a PPMC, the IPMC is > > to be notified that that vote is happening. IPMC members are > > encouraged to participate in the vote process on the PPMC list where > > it is happening. > > This has been discussed before and I’m not sure the IPMC has the bandwidth for this.
[DISCUSS] IPMC votes on releases)
On Wed, Aug 14, 2019 at 1:24 AM Justin Mclean <justin@classsoftware.com> wrote: > > Hi, > > >> This is because of ASF bylaws i.e only PMC votes are binding on releases. > > > > That is not in the Bylaws. Stop making stuff up. > > That the way it’s been explained to me, several times, by experienced ASF people, that only PMC votes are binding on releases and podlings are not mentioned in the ASF bylaws.
Podlings, the Incubator, relationships and Apache
On Thu, Jun 27, 2019 at 7:57 AM Greg Stein <gstein@gmail.com> wrote: > > On Thu, Jun 27, 2019 at 12:13 AM Justin Mclean <justin@classsoftware.com> > wrote: > > > > b) It listed as a TLP in Whimsy > > Whimsy is not canonical. Its label means absolutely nothing. Board > decisions are canonical. The canonical source is: https://svn.apache.org/repos/private/committers/board/committee-info.txt This source is nearly always updated via Whimsy roster tool as that keeps LDAP in sync.
Podlings, the Incubator, relationships and Apache
On Mon, Jun 24, 2019 at 12:12 PM Roman Shaposhnik <roman@shaposhnik.org> wrote: > > On Sun, Jun 23, 2019 at 11:03 PM Alex Harui <aharui@adobe.com.invalid> wrote: > > > > But, IMO, the reason the question went to VP Legal is that it doesn't really matter what the IPMC thinks if their "business decision" will have an impact on the "Legal Shield" and the insurance premiums that go with it. So I think the question got lost on legal-discuss.
[IMPORTANT] Board proposal on podling releases
On Fri, Jun 7, 2019 at 8:57 PM Justin Mclean <justin@classsoftware.com> wrote: > > Hi, > > > 1) Is it legal to include GPL licensed software in releases? The > > answer is yes... as long as we comply with the terms of that license. > > In the case of strong copyleft licenses, that could mean that the > > podling release itself may need also be GPL licensed. > > And in cases where this has happened, it’s been ALv2 licensed, so I guess that wouldn’t be legal.
[IMPORTANT] Board proposal on podling releases
On Fri, Jun 7, 2019 at 2:00 PM Craig Russell <apache.clr@gmail.com> wrote: > > Hi Justin, > > As a board member, I'm not comfortable with granting a blanket exception to policy that might put us at legal risk. > > As an IPMC member, I think that we do not want to allow podlings to release material that might put us at legal risk. I do think that the IPMC under today's policy has the ability to decide whether a podling release puts us at risk and therefore should be blocked.
Podling releases and release policy
On Sat, Jun 1, 2019 at 7:50 PM Justin Mclean <justin@classsoftware.com> wrote: > > Hi, > > > Point me to where you are not allowed to make non-official podling releases > > that conform to Incubator policy. > > I find that hard to parse and perhaps you meant don’t conform to incubator policy? But either way it’s not incubators policy, it’s the boards and infra policy. Been lurking.
Generating + formatting the Board report from the website?
On Wed, May 22, 2019 at 10:26 AM Justin Mclean <justin@classsoftware.com> wrote: > > Hi, > > > Doesn't the new Markdown format help with that? > > I hope it will but: > a) Messy markdown with inconsistent formatting can still look good. > b) Some podlings submit at the last minutes and ignore formatting. > c) Some podlings tend to copy and paste the last report and modify and may miss/alter the markdown. > > We’ll see what happens.
Generating + formatting the Board report from the website?
On Wed, May 22, 2019 at 8:28 AM Justin Mclean <justin@classsoftware.com> wrote: > > Hi, > > > - Whimsy likes 80 column linewraps. It will only rewrap the current > > report if you push the rewrap button and then commit. It doesn't ever > > wrap long URLs. > > Currently that severely breaks the incubator report so I don’t use it. Also any edits to the incubator report in Whimsey duplicates large sections of it. Both of these issues are known.
Generating + formatting the Board report from the website?
On Wed, May 22, 2019 at 5:46 AM Justin Mclean <justin@classsoftware.com> wrote: > > Hi, > > > Do you then mean to run "fold -w 76 cat -s" on the formatted Markdown > > to prepare it for the Board report? > > Yes, as your experiment is still of use. Someone somewhere is still going to view it in text form. > > It’s still unclear to me how Whimsy will render this, guess we find out when we submit it? > > > That seems to work fine as the basic formatting is now clean.
board report duplication
On Sat, Apr 13, 2019 at 5:54 PM Ted Dunning <ted.dunning@gmail.com> wrote: > > Moving to a data format that makes a stronger distinction between content > and envelope might be nice. JSON would work if content is actually quoted > (don't bet on it). A directory would probably be better because the content > of a file can't break the meta-data in the directory. Something like a real > database would be even better.
board report duplication
On Sat, Apr 13, 2019 at 7:29 AM Shane Curcuru <asf@shanecurcuru.org> wrote: > > Sam Ruby wrote on 4/12/19 9:48 PM: > > On Fri, Apr 12, 2019 at 2:42 PM Sam Ruby <rubys@intertwingly.net> wrote: > >> > >> 3) Somebody uses the whimsy board agenda tool to update the incubator > >> report, and it dutifully strips out the previous report (up to said > >> row of dashes) an inserts a new report.
board report duplication
On Fri, Apr 12, 2019 at 6:19 PM Justin Mclean <justinmclean@me.com> wrote: > > Hi, > > > 3) Somebody uses the whimsy board agenda tool to update the incubator > > report, and it dutifully strips out the previous report (up to said > > row of dashes) an inserts a new report. > > It’s a bug in whimsey that cause the reports to be doubled I’ll check today and fix in SVN if needed but the only issue shod be sign off and comment on Spot.
board report duplication
On Fri, Apr 12, 2019 at 2:42 PM Sam Ruby <rubys@intertwingly.net> wrote: > > 3) Somebody uses the whimsy board agenda tool to update the incubator > report, and it dutifully strips out the previous report (up to said > row of dashes) an inserts a new report.
board report duplication
On Fri, Apr 12, 2019 at 12:12 PM Myrle Krantz <myrle@apache.org> wrote: > > Hey incubator, > > It looks like part of the incubator report was "doubled". I've deleted the > duplication, but I'd appreciate it if you'd check me to be sure I didn't > accidentally delete something that belonged. I still see duplication? TOC starting on line 2958 and 4206?
[RFC] Mentors and podling LDAP memberships
Yes, yes, not necessarily. First: " For that reason, I'd like to make a simplifying assumption: that all mentors are PPMC members, and all PPMC members are committers. " -- https://lists.apache.org/thread.html/a6ce7e3a366490f04f5c66e9434aa2b7da9a763f040262f1b12407af@%3Cgeneral.incubator.apache.org%3E As to your third question... I guess it would be possible (but weird) for somebody to want to stop as a mentor but continue as a committer (and possibly a PMC member).
Clarifying on how to add initial PPMC members
On Mon, Dec 18, 2017 at 6:43 AM, John D. Ament wrote: > Heyyy look at that, it's magic (check your email). You should be all set. > > But I should replace "requested" with "completed" to make sure people know > that it has to be done first. And as far as I know, it is a button, > however only infra and secretary can push that button. Correct. The authority required to execute that request is the same authority required to delete (or modify) any PMC or podling.
Agile Web Development with Rails 5.1
Where’s the cart? Now you can get everything on Safari . To purchase books, visit Amazon or your favorite retailer. Questions? See our FAQ or contact customer service: Learn Rails the way the Rails core team recommends it, along with the tens of thousands of developers who have used this broad, far-reaching tutorial and reference. If you're new to Rails, you'll get step-by-step guidance.
Re: svn commit: r1802207
On Tue, Jul 18, 2017 at 1:28 PM, Jim Apple wrote: > The rosters are then hidden from people who aren't committers on some ASF > project, yes? Saying "in whimsy" is shorthand. The data is stored in LDAP. Whimsy provides a web interface to update LDAP. Yes, that interface is committer only. The plans are to have the Apache Phonebook display this information from LDAP (most likely by requesting and then parsing public JSON versions of this information from the whimsy server).
[DRAFT] What the new Status Pages potentially look like
On Thu, Jun 15, 2017 at 1:21 PM, Jim Apple wrote: > Here are some suggestions: > > 1. Only make this the reporting structure for new podlings. > Grandfather in old podlings to the old structure, since they may > already have workflows built around it. Impala does. We don't need to delete the old structure; but we will soon get to the point where there is tooling that depends on the new structure being in place.
[DRAFT] What the new Status Pages potentially look like
On Tue, Jun 13, 2017 at 9:04 PM, John D. Ament wrote: > Jim, > > For your specific cases, if all you want is to remove red text: > > - for :sga: enter the date in YYYY-MM-DD format of when the ASF Secretary > acknowledged your SGA. Based on the records I have its 2016-03-15 > - For the :asfCopyright: and :distributionRights: attributes, I would use > 2017-01-20 as that's the day of the results of 2.8 which was the first > release to have no issues during review.
Updating PPMC rosters via whimsy
On Sun, Jun 11, 2017 at 7:58 AM, John D. Ament wrote: > On Sun, Jun 11, 2017 at 5:58 AM sebb wrote: > >> On 11 June 2017 at 00:18, Sam Ruby wrote: >> > On Fri, May 26, 2017 at 6:10 PM, Sam Ruby >> wrote: >> >> >> >> For that reason, I'd like to make a simplifying assumption: that all >> mentors >> >> are PPMC members, and all PPMC members are committers.
Updating PPMC rosters via whimsy
Sorry about that. Fixed. Thanks for reviewing the output! - Sam Ruby On Sun, Jun 11, 2017 at 12:31 PM, Adina Crainiceanu wrote: > John, > > I'm a committer and PPMC member for Rya > > Adina > > On Sun, Jun 11, 2017 at 12:23 PM, John D. Ament > wrote: > >> Adina, >> >> What podling are you on?
[DRAFT] What the new Status info looks like
On Sat, Jun 10, 2017 at 11:20 AM, John D. Ament wrote: > > - List of repositories. For github it's easy, we can just link to a > search. Can't say the same for ASF hosted (yet) Would these help? https://svn.apache.org/repos/asf/incubator/ https://gitbox.apache.org/repos/asf - Sam Ruby P.S. How does one search github? https://github.com/orgs/apache/repos doesn't appear to work, despite what https://developer.github.com/v3/repos/#list-your-repositories seems to imply.
Updating PPMC rosters via whimsy
On Fri, May 26, 2017 at 6:10 PM, Sam Ruby wrote: > > For that reason, I'd like to make a simplifying assumption: that all mentors > are PPMC members, and all PPMC members are committers.
Contents of Podling Status Tracking
On Tue, Jun 6, 2017 at 7:49 AM, John D. Ament wrote: > On Tue, Jun 6, 2017 at 7:44 AM Sam Ruby wrote: >> >> Some of the data that you mentioned doesn't need to be in the status >> file as it can be generated from other sources. For example: >> https://whimsy.apache.org/board/agenda/json/podlingnamesearch. I'll >> refactor that code and add that information to the ppmc pages of the >> roster tool. > > I don't see the code that generates this. Where did it come from?
Contents of Podling Status Tracking
On Tue, Jun 6, 2017 at 7:43 AM, Sam Ruby wrote: > > YAML is more human editable than JSON. As Sebb points out elsewhere, > it also supports comments. Alternative: create DOAP files for podlings. In general, model podlings like PMCs as much and as soon as possible. - Sam Ruby --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org
Contents of Podling Status Tracking
Not sure where to comment, so I'll top post. Some of the data that you mentioned doesn't need to be in the status file as it can be generated from other sources. For example: https://whimsy.apache.org/board/agenda/json/podlingnamesearch. I'll refactor that code and add that information to the ppmc pages of the roster tool. YAML is more human editable than JSON. As Sebb points out elsewhere, it also supports comments.
[NOTICE] Community Vote for Apache Atlas Graduation to TLP
On Mon, Jun 5, 2017 at 3:17 PM, Suma Shivaprasad wrote: > Thanks Sam. Have added the rest of the PPMC/committers. Cool! For future reference, you can click on + multiple times to queue up additions, and then add them all at once. Also, take a look at the "Draft graduation resolution" at the bottom of the page. It can help you draft a resolution that contains correct names and IDs, etc.
[NOTICE] Community Vote for Apache Atlas Graduation to TLP
On Thu, Jun 1, 2017 at 6:25 PM, Suma Shivaprasad wrote: > > Once the issues are rectified, will work with one of the mentors to update > https://whimsy.apache.org/roster/ppmc/atlas I've added you; you should now be able to add the rest. The PPMC will be notified of your changes.
[NOTICE] Community Vote for Apache Atlas Graduation to TLP
On Thu, May 25, 2017 at 8:45 PM, John D. Ament wrote: > Hi Suma, > > Thanks for the heads up. There is actually no requirement for the podling > community to vote on graduation, but its a good sign. > > I'm a little concerned, can you double check your status file at [1] ? > Most of the items are marked N/A which is weird, most of these should > actually have dates. > > In addition, can you provide a list of committers you have added since > starting at Apache?
Updating PPMC rosters via whimsy
On Fri, May 26, 2017 at 10:18 PM, Sam Ruby wrote: > On Fri, May 26, 2017 at 9:19 PM, John D. Ament wrote: >> On Fri, May 26, 2017 at 6:10 PM Sam Ruby wrote: > >>> Adding a new committer, PPMC member, or mentors should be a matter a few >>> mouse clicks and selecting the name. LDAP and/or podlings.xml will be >>> updated on your behalf. >>> >> FWIW, I just tried adding you as a mentor to a podling, it failed with a >> 500 ISE. > > I neglected to mention that that isn't implemented yet.
Updating PPMC rosters via whimsy
On Fri, May 26, 2017 at 9:19 PM, John D. Ament wrote: > On Fri, May 26, 2017 at 6:10 PM Sam Ruby wrote: > >> Gitbox has been updated, our ponymail installation has been updated, our >> svn server will be updated soon. Other services will be updated as well. >> > What about regular git-wip-us? Probably, but if not, it will be soon. >> Adding a new committer, PPMC member, or mentors should be a matter a few >> mouse clicks and selecting the name.
Updating PPMC rosters via whimsy
TL;DR: podling membership lists are being consolidated to LDAP, podling mentor lists remain in podlings.xml; the whimsy roster tool is being updated to become a one-stop-shop that can be used to update everything. For the impatient, a link: https://whimsy.apache.org/roster/ppmc/trafodion Feedback welcome on the proposal below. Fair warning: I'll treat any lack of input as lazy consensus.
private list subscriptions
On Mon, May 22, 2017 at 3:42 PM, Jim Jagielski wrote: > >> On May 22, 2017, at 12:43 PM, sebb wrote: >> >> Whimsy auto-subscribe only allows committers to use their ASF address >> or the ones listed in thei LDAP record. > > That seems, to me, a restriction that Whimsy should fix... > None of my subscriptions to any private PMC lists that I'm on > are with my a.o address, and I'm guessing I'm not unique there.
Revisit policy that all IPMC members have commit privs to all incubator repositories.
On Mon, Apr 10, 2017 at 3:38 AM, Bertrand Delacretaz wrote: > On Sat, Apr 8, 2017 at 8:23 PM, Sam Ruby wrote: >> ...Can I just work with the infrastructure team to >> make this happen? Do we need a formal vote?.. > > As Marvin explains very well I don't think we need a formal vote but > I'd like whatever actions are taken, as well as their motivations, to > be briefly documented in an > https://issues.apache.org/jira/browse/INCUBATOR ticket. Or INFRA > ticket linked here.
Revisit policy that all IPMC members have commit privs to all incubator repositories.
On Mon, Apr 10, 2017 at 9:24 AM, Bertrand Delacretaz wrote: > On Mon, Apr 10, 2017 at 1:55 PM, Sam Ruby wrote: >> ...The very first line of this thread is a link to an INFRA ticket. A >> comment on that ticket links to this very thread...
Revisit policy that all IPMC members have commit privs to all incubator repositories.
On Sun, Apr 9, 2017 at 11:09 AM, John D. Ament wrote: > On Sat, Apr 8, 2017 at 2:23 PM Sam Ruby wrote: > >> What's the next step? Can I just work with the infrastructure team to >> make this happen? Do we need a formal vote? >> > Can you clarify what exactly you're going to ask infra to change? I see > that infra has made a gitbox specific change, I would expect to see a > incubator-wide change. I'm not certain I've got a crisp answer. I'm also not looking to make any quick changes.
Revisit policy that all IPMC members have commit privs to all incubator repositories.
On Sun, Apr 9, 2017 at 6:29 PM, John D. Ament wrote: > [...] > 3. The interface itself needs to be able to track committers and PPMC > members differently. I've created > https://issues.apache.org/jira/browse/WHIMSY-84 to track this need (since > all committers == all members, but not all members are on the PPMC) >From an implementation perspective, I've got that code for PMCs so it will be easy to add.
Revisit policy that all IPMC members have commit privs to all incubator repositories.
What's the next step? Can I just work with the infrastructure team to make this happen? Do we need a formal vote? - Sam Ruby On Thu, Apr 6, 2017 at 1:06 AM, Sam Ruby wrote: > Background, from https://issues.apache.org/jira/browse/INFRA-13804 > >> With this feedback and review, I believe we're still operating as >> expected. >> >> * Per current policy, IPMC members have commit privileges on all Incubator >> repositories.
Revisit policy that all IPMC members have commit privs to all incubator repositories.
John, your email confuses me for many reasons. On Thu, Apr 6, 2017 at 6:57 AM, John D. Ament wrote: > This solution describes one of the many reasons I feel the incubator itself > is broken. We're trying to rewrite policy, as a means to work around some > awkward setup sitting around, instead of just treating podlings as regular > projects, with some restrictions in place. What I am proposing is to indeed tread podlings more like regular projects, with some restrictions in place.
Revisit policy that all IPMC members have commit privs to all incubator repositories.
Background, from https://issues.apache.org/jira/browse/INFRA-13804 > With this feedback and review, I believe we're still operating as expected. > > * Per current policy, IPMC members have commit privileges on all Incubator repositories.
LDAP changes to support podlings
On Wed, Jan 18, 2017 at 8:51 PM, John D. Ament wrote: > On Wed, Jan 18, 2017 at 8:25 PM Sam Ruby wrote: > >> On Wed, Jan 18, 2017 at 1:37 PM, Felix Meschberger >> wrote: >> > >> > Hi Sam >> > >> > Like this very much.
LDAP changes to support podlings
On Wed, Jan 18, 2017 at 1:37 PM, Felix Meschberger wrote: > > Hi Sam > > Like this very much. Thanks ! > > Started doing that for OpenWhisk and realized some strange UI behaviour: > To add a PPMC member I have to click + then search for the user, click on + > again and then click on „Add to PPMC“ button > > What is the reason for the last „Add to PPMC“ button click ? This somehow > breaks the otherwise nice experience. Or would it be possible to batch-add > multiple members ?
LDAP changes to support podlings
On Mon, Jan 16, 2017 at 1:05 PM, Sam Ruby wrote: > Current status: for ppmcs that have lists in the subversion puppet > definitions, those lists have been loaded into LDAP, and augmented with > mentor information from podlings.xml.
LDAP changes to support podlings
On Tue, Jan 17, 2017 at 1:57 PM, John D. Ament wrote: > On Tue, Jan 17, 2017 at 1:11 PM Sam Ruby wrote: > >> On Mon, Jan 16, 2017 at 1:31 PM, Stian Soiland-Reyes >> wrote: >> > Not sure what was the decision to be made here, but +1 to all >> suggestions. >> > All of PPMC as podling owners makes sense to me as long as >> private@podling >> > is notified. >> >> The following four podlings don't have private@podling lists: >> ["log4cxx2", "odftoolkit", "ratis"]. >> > private@logging and odf-private.
LDAP changes to support podlings
On Mon, Jan 16, 2017 at 1:31 PM, Stian Soiland-Reyes wrote: > Not sure what was the decision to be made here, but +1 to all suggestions. > All of PPMC as podling owners makes sense to me as long as private@podling > is notified. The following four podlings don't have private@podling lists: ["log4cxx2", "odftoolkit", "ratis"]. ratis being a clear example of 'not yet'. So a revised approach: emails go to private@podling list, if there is one.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Sam
Contact Sam, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack