Re: Mentors wanted for Apache Annotator (incubating)
Hi, Benjamin-- I'm very interested in Annotator (especially, as an apache Jena committer, from the linked data side) so I'd be happy to mentor. Adam Soroka On 2018/10/12 14:43:54, Benjamin Young wrote: > Don't everybody sign-up at once, k?! ;-P > > We're a pretty easy-to-mentor project, fwiw. Two of our PPMC members are > experienced committers to the Apache CouchDB project. We mostly need help > with signing off on board reports, helping expand the reach and interest > (within Apache mostly) of the Apache Annotator (incubating) project. > > Nick has been a fabulous mentor (as were his overly-busy predecessors), but > we can't run on just his singular amazingness...which is where *you* come in. > :) > > Please volunteer just a bit of your time to help us navigate the halls of the > ASF. > > Thanks! > Benjamin > > > -- > > http://bigbluehat.com/ > > http://linkedin.com/in/benjaminyoung > > > From: Benjamin Young > Sent: Friday, October 5, 2018 1:13 PM > To: general@incubator.apache.org > Subject: Mentors wanted for Apache Annotator (incubating) > > Hi all! > > We've recently had several mentors bow out of mentoring due to their other > responsibilities becoming more pressing. Consequently, we're looking to add > 2-3 more folks who can help us navigate the Incubator process. > > http://annotator.apache.org/ has more information if you're new to the > project. > > Our greatest incubator related hurdle is wrangling a scattered community from > across the Web into the welcoming arms of our project. :) We're building > tooling around the W3C's Web Annotation specifications [1] and writing > browser and server code to eventually replace much of the tooling originally > provided by Annotator.js [2]. However, our goal is *not* to ship a full UX > for doing annotation, but rather a set of tools to enable developers to ship > annotation capabilities within their applications. > > You can read more about our project on our Proposal page: > https://github.com/apache/incubator-annotator/wiki/Proposal > > We hope to eventually be able to liaison with many other Apache Top-Level > Projects to add annotation capabilities to their systems for machine > learning, linked data, and natural language processing (search, indexing, > etc). > > Help wanted! :) > > Much thanks! > Benjamin > > [1] https://www.w3.org/annotation/ > [2] http://annotatorjs.org/ > > > -- > > http://bigbluehat.com/ > > http://linkedin.com/in/benjaminyoung > ajs6f - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: How to review so-called "binary releases"?
Another example: for some projects, the most important distribution is via Maven Central. We can distribute source and binary there, of course, but my guess would be that the vast majority of consumers are pulling the binaries and linking directly against them, using source distributions only for UX/UI assistance in their IDEs, and for Apache dependencies they require in an automated build, maybe not even that. ajs6f > On Nov 7, 2018, at 10:23 AM, Dave Fisher wrote: > > Hi - > > There are some projects where the binary is all the users want. For example, > Apache OpenOffice. In that case these binaries are an exception and while on > dist they are not mirrored and instead we distribute through SourceForge. > > I think if binaries are kept in a separate folder from source then > DISCLAIMERs could be required to be added. > > To move to a new url would be very disruptive. To tell projects that they can > no longer distribute binaries for community convenience would not be a small, > reversible change. > > Regards, > Dave > > Sent from my iPhone > >> On Nov 7, 2018, at 5:14 AM, Carlos Santana wrote: >> >> Jim >> >> What do you think now? >> Was that a good or bad thing? >> >> TLDR; I’m in favor of convenient binaries is just the how they are handled. >> >> Sorry for my brevity, what I meant is that binaries should not be beside >> next to the source release seating on the same server and giving the same >> guarantees for both type of artifacts (source vs binary). >> >> Now in terms of convenience :-) >> ASF should not block a project of making binaries available to their >> community for what ever purpose they think appropriate (ie nightly, binary >> of a RC, binary of final RC) >> >> ASF should provide guidance to the projects to make sure they make their >> communities aware that a source artifact is different from a binary >> artifact. >> A project for example can put warnings and bold text on the location (ie >> directory, readme, inside the binary, download webpage, wiki etc) where the >> community downloads a copy of the binary. >> The warning can say this is not a release of the ASF, is just a convenient >> binary “download on your own risk”, we provide sha256 sum and maybe the >> binary is even signed, but best practice is for you to download the source >> and be in control of building the binary. >> >> >> >> - Carlos Santana >> @csantanapr >> >>> On Nov 7, 2018, at 7:04 AM, Jim Jagielski wrote: >>> >>> Just a FYI that in the early days of the ASF (and the httpd project), >>> community binaries were a common offering... >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Font size on incubator site too small?
+1 On Thu, Nov 28, 2019, 5:25 AM Andy Seaborne wrote: > Or default to the user's choice of font family in the browser. > > On 28/11/2019 06:01, Dave Fisher wrote: > > Reading glasses will enlarge things for many of us. > > > > I’m certainly in favor a larger font, but please keep it serifed. > > > > Sent from my iPhone > > > >> On Nov 27, 2019, at 11:48 PM, Ted Dunning > wrote: > >> > >> The problem might just be that pixels are getting smaller. > >> > >> > >> > >>> On Thu, Nov 28, 2019 at 12:15 AM Justin Mclean < > jus...@classsoftware.com> > >>> wrote: > >>> > >>> Hi, > >>> > >>> Is it just my old eyes or do other people also find the font size too > >>> small on the incubator site? While it does scale well and easy for a > user > >>> to increase the size, have we set the default too small? This may of > course > >>> depend on platform and browser use and I’ve not done any exhaustive > >>> checking, as the measurement is in px that may be the issue. The body > text > >>> seem to be set to 14px, (which is 10.5pt and that should be in pt or > ems > >>> not px) and 12pt (16px) is generally recommended as a minimum size. > >>> > >>> Thanks, > >>> Justin > >>> - > >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >>> For additional commands, e-mail: general-h...@incubator.apache.org > >>> > >>> > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
