+1 ... LGTM.
@j...@apache.org good catches.
@ALL -- Which of the release steps do we think could be more automated and
less manual? Yes, we still will have manual steps, but it might be worth
investing in some repeatable scripts. For those that have done
more thorough releases and/or
On: ASF Admin's don't understand project health due to repo structure --
i disagree with the idea that itshould at all inform/dictate how work gets
structured and completed by the Flagon project.
I am not sure I understand how documentation improves by having a
monorepo. I guess if pitched about
This would be worth asking ASF Infra. I would hope that's something that
could be largely automated, though - if memory serves - we need a human to
choose to perform [ ex: trigger ] the release.
That also invites how authentication is happening -- definitely I prefer
short-lived credentials,
ttps://people.apache.org/phonebook.html?pmc=flagon>
> [image: favicon.ico] <https://people.apache.org/phonebook.html?pmc=flagon>
> <https://people.apache.org/phonebook.html?pmc=flagon>
>
>
> - Jason
>
> On Oct 18, 2023, at 2:55 PM, Austin Bennett wrote:
>
> Great
What's the plan?
On Sat, Oct 21, 2023, 10:39 AM lewis john mcgibbney
wrote:
> I’m here.
> lewismc
>
> On Sat, Oct 21, 2023 at 08:28 Christofer Dutz
> wrote:
>
>> Hi all,
>>
>>
>>
>> I was tasked at the last board report to pursue a roll call for Apache
>> Flagon after we saw that a VOTE thread
Great, thanks, congratulations -- I haven't dug in, yet, but sufficient
votes are in! Naturally, gotta wait the 72 hours, but seems the release
likely to go out!
On Wed, Oct 18, 2023 at 11:42 AM Amir Ghaemi wrote:
> Hi all,
>
> +1
> Great work!
>
> [✓] Build and Unit Tests Pass (On Windows -
Generally, I'd imagine minor releases. Unless breaking changes. So,
sounds like this suffices.
Time to dig into our release process and testing. Specifically, wondering
what all additionally will people potentially do manually - since would
want to work towards systematizing and automating.
implemented GitHub wikis via asf.yaml just for fun. Was thinking
> about putting in release procs. there at minimum.
>
> We saved dev!
>
> -J
>
> > On Jun 15, 2023, at 9:56 PM, Austin Bennett wrote:
> >
> > Sounds great - thanks for digging into getting this cl
16 PM, Joshua Poore wrote:
> >>
> >> OK, I have requested the Notifications list. I’ll push subscribe
> details out when it’s available (approx 24hrs).
> >>
> >> Going to experiment with asf.yaml mods on apache/flagon repo next.
> >>
> >>> On Ju
, 2023, 9:00 PM Joshua Poore wrote:
> Regretfully, I’m not. wish I could be more helpful.
>
> > On Jun 11, 2023, at 6:33 PM, Austin Bennett wrote:
> >
> > Hi Flagon Devs,
> >
> > Is anyone else familiar with Nix? ( if we had shell configs, would
> t
gt; <https://github.com/apache/plc4x/blob/e14a3d7dc8bae8ead824f019d5e87767c4460adc/.asf.yaml#L61>
>
>
> Did I miss anything?
>
> Josh
>
> On Jun 11, 2023, at 9:54 PM, Austin Bennett wrote:
>
> Hi Flagon Dev,
>
> How do we feel about using a notifications@
on devlist, for things my GH
user is apart of?
To: Austin Bennett
Cc: ,
You'd really have to try to convince your project to configure their
.asf.yaml file to send their GH notifications to a secondary list
(like notifications@) which you can simply unsubscribe from, so you
don't get duplicates from
> the dev@ list, at their choice. Some projects do this, while others
> are much more resistant to the idea, and would prefer you just
> configure your mail client to filter things out manually.
>
> On Sun, Jun 11, 2023 at 6:40 PM Austin Bennett wrote:
> >
> > Hi Infra U
Hi Flagon Devs,
I'd like to surface issues with tags to make it clear what components might
be easier to address, and/or where newcomer help would be especially
welcome. This is in service towards getting practices/thoughts on list :-)
Some projects have issues tied to each individual
Hi Infra Users,
The Flagon project currently receives GH notifications to the dev list.
I'd prefer to not receive emails for Issues/Comments I am
already participating in [ as it otherwise feels like spam ], is there a
way to customize this so it does not get sent to me? I write here since in
Hi Flagon Devs,
Is anyone else familiar with Nix? ( if we had shell configs, would those
be used/enjoyed by anyone else? )
If not at all of interest to anyone else, that makes it less interesting to
create - the benefit I get from those is via collab.
Curious your thoughts,
Thanks,
Austin
Do we have the ability to customize these messages? Ex: I would prefer
not to see issues I'm filing. Can this be handled serverside?
On Sun, Jun 11, 2023 at 3:29 PM brucearctor (via GitHub)
wrote:
>
> brucearctor opened a new issue, #34:
> URL: https://github.com/apache/flagon/issues/34
>
>
Hi Flagon Devs,
Does anyone else have experience with protobuf/gRPC. Support is increasing
for web, so it will eventually make sense to use. Is it too early now?
Does this concern people to also support? Concretely, I tend to rip
JSON/REST out of most code I touch, for the performance
that comment sounds like then the move would be
then to pipe PRs/etc to Slack <https://github.com/integrations/slack>,
Discord, etc if students not doing much with email lists. I would imagine
increasing noise [ any comment on any issue/PR would only discourage people
to read, but ...? ].
>
merges between master and asf-site.
>
> > On Jun 9, 2023, at 10:13 PM, Austin Bennett wrote:
> >
> > sounds great ... Do you think we need to writeup issues, and see if
> > concrete/bite-size enough to get any committers or
> > contributors/future-committers
TEST:
Does this comment go to GH as well? Otherwise, I think there is a
usability problem with piping issue/pr comments to a list, and then the
reply doesn't work to send back there. Let's see.
Also, agreed, thanks, @Jyyjy !
On Fri, Jun 9, 2023 at 6:40 PM poorejc (via GitHub) wrote:
>
>
sounds great ... Do you think we need to writeup issues, and see if
concrete/bite-size enough to get any committers or
contributors/future-committers to help address?
Anyone have an interest and bandwidth to address?
On Fri, Jun 9, 2023 at 6:56 PM Joshua Poore wrote:
> Recent PR from Austin
Since was discussed on another the other thread -- I find this noise by
being on dev list.
On Mon, Jun 5, 2023 at 10:37 PM brucearctor (via GitHub)
wrote:
>
> brucearctor commented on PR #29:
> URL: https://github.com/apache/flagon/pull/29#issuecomment-1577940757
>
>@poorejc -- what's our
Dependabot opens PRs, why treat that differently than other PRs? So, I'm
at least a +1 on both 1 and 2 [ but suggest they be the same list? ].
For 4 --> Any reason people can't just subscribe themselves to
notifications [ via 'watch' ]?
https://summerofcode.withgoogle.com/
There are possibilities to take on students via GSOC under the ASF
umbrella. I have mentored for GSOC in the past. Putting on Flagon's
radar, in case interested in mentoring some students into Open Source.
Supportive of that.
Would encourage us to also communicate more general guidance on what the
community intends to support [ or can expect ]. An example --> "We support
3 versions of Node, at least 2 of which are LTS". Or something similar.
Good for website, README, etc...
Also, very strongly
refox/Edge, since the change isn't backwards
> compatible. With that in mind, it may be wise for us to
> temporarily/permanently keep an older Manifest V2 version published.
> >
> > Regards,
> > Rob
> >
> > On 8/29/2022 9:49 PM, Austin Bennett wrote:
VOTE’d.
> Thanks
>
> On Sat, Nov 5, 2022 at 15:37 Austin Bennett
> wrote:
>
> > On this thread, we have 6 +1s [ also another on the incubator thread ]
> and
> > no 0, or -1 votes, so* the VOTE passes*, and we can confidently say the
> > community is in favor of Gradua
Jones
Austin Bennett
There were no votes against.
Best,
Austin
[1] https://lists.apache.org/thread/vlhrb87f6s4wmckkwrh2v3toj06zhhbp
[2] https://lists.apache.org/thread/po7g4b51mp6nb2khvkpxd8r0gv4qsh34
[3] https://lists.apache.org/thread/xbkg9mcwx23c1235013ownyxss31rkpc
t; >> >
> >> > > Emphatic +1 for me.
> >> > >
> >> > > Sincerely,
> >> > >
> >> > > Josh
> >> > >
> >> > >
> >> > > On Oct 31, 2022, at 5:13 PM, lewis john mcgibbney <
Hi Flagon Community,
Given recent discussions around the graduation status of the project, it is
time to work through the process. We have had a recent discussion on-list,
and consensus seems to be in favor of graduation. The next step seems to
be a recommendation that we make an official VOTE,
ion.
>
> Rob
>
> On 10/22/2022 1:44 PM, Austin Bennett wrote:
> > +1
> >
> > Graduation a great step, I am in favor.
> >
> > I would like to see a bigger community [ of public users, and
> contributors
> > ], and those from different organiza
+1
Graduation a great step, I am in favor.
I would like to see a bigger community [ of public users, and contributors
], and those from different organizations. But, graduation may help that -
as being graduated is a strong signaling mechanism.
On Sat, Oct 22, 2022 at 9:52 AM Gedd Johnson
Great, thanks josh!
On Mon, Sep 26, 2022, 7:23 PM Joshua Poore wrote:
> Good news!
>
> I think we’re clear on all our actions following the CCLA and SW Grant.
>
> I’ve pushed the SW grant to the Apache Flagon Distill repo (
> https://github.com/apache/incubator-flagon-distill <
>
er. How’s that?
>
> > On Aug 29, 2022, at 9:24 PM, Austin Bennett
> wrote:
> >
> > That is certainly a way to do it that seems better than the current
> > approach? Hoping to get as automated as feasible.
> >
> > Is there a reason you'd want package.js
> > On Aug 26, 2022, at 11:42 AM, Austin Bennett <
> whatwouldausti...@gmail.com> wrote:
> >
> > Hi Devs,
> >
> > We have Dependabot in the repository which is suggesting maintenance PRs
> to
> > bump versions -->
> >
> https://github.com/
Hi Devs,
We have Dependabot in the repository which is suggesting maintenance PRs to
bump versions -->
https://github.com/apache/incubator-flagon-useralejs/pulls/app%2Fdependabot
What are your thoughts around how to treat those PRs?
* Turn off?
* Just [manually] merge? We do have some tests,
Hi Flagon-Dev,
Do we have a Flagon community standard for when OK to merge a PR?
Inviting us to have a discussion, and to get consensus around community
standards for reviewing PRs/when-OK-to-Merge. Apologies if I missed a
prior discussion/doc on this topic.
I assume we ultimately need a
The details shared in the email sound great. Will follow up after reading
the links, in the event anything seems really concerning.
On Tue, May 31, 2022, 6:49 PM Joshua Poore wrote:
> Hi All,
>
> I’m very excited to say that the University of Maryland has executed an
> CCLA with Software
Thanks, all -- glad to be voted in to be even more a part of the community,
and looking forward to seeing the things we will develop!
On Thu, May 26, 2022 at 7:42 PM Joshua Poore wrote:
> All--
>
> I am pleased to Announce that Austin Bennet has been added as a Committer
> and PPMC member
great - thanks for sharing!
On Tue, May 24, 2022 at 7:12 AM Joshua Poore wrote:
> Hi All,
>
> For your reading enjoyment:
>
> My team at University of Maryland presented a paper on our work on Distill
> to the 2022 AAAI Spring Symposium on AI Engineering. Our paper is now
> available as a
ll IPMC.
>
> Apologies for the delay in the release VOTE. I should have delegated
> earlier in light of havoc at home.
>
> > On May 7, 2022, at 10:11 PM, Austin Bennett
> wrote:
> >
> > Furkan,
> >
> > Trying to understand the process, esp. understand PPMC, IPMC,
,
>
> We have 3 binding votes (Joshua Poore, Gedd Johnson, Furkan KAMACI) and 1
> non-binding vote (Austin Bennett).
>
> So, the vote has passed in terms of the ASF rules.
>
> Kind Regards,
> Furkan KAMACI
>
> On Sun, May 8, 2022 at 3:21 AM Austin Bennett >
ng closed or not?
>
> Kind Regards,
> Furkan KAMACI
>
> On Tue, May 3, 2022 at 10:04 PM Austin Bennett <
> whatwouldausti...@gmail.com>
> wrote:
>
> > Based on what has been checked, it looks good to me, so +1 ( non-binding
> > ).
> >
> &
Based on what has been checked, it looks good to me, so +1 ( non-binding
).
A process questions to ensure things get covered, long term:
* is there a concrete list for things actually desired to be checked as
part of release process ( I see some things, ex:
+1 (non-binding, etc)
Though... should this be public/on-dev-list?
On Thu, Mar 18, 2021 at 6:00 PM Joshua Poore wrote:
> +1 from me (Flagon PPMC)
>
> > On Mar 18, 2021, at 8:59 PM, Joshua Poore wrote:
> >
> > Hello,
> >
> > I am calling a VOTE to add Gedd Johnson (@UncleGedd) to the Apache
>
In general more testing == better (at least until extreme).
Glad for that topic to be pushed. And, welcome, @Gedd!
(from someone that mostly lurks/follows the community, rather than doing
much by way of actually contributing thus far!).
On Mon, Mar 15, 2021 at 8:35 AM Rob Foley wrote:
>
+1 -- based on rationale's listed.
On Sun, Jan 26, 2020 at 8:55 PM Joshua Poore wrote:
>
> Hi Folks,
>
> I’m sorry for the delay. I’m going to call this to a VOTE. We’re going to go
> with a Lazy Consensus on this one, meaning if “silence is acceptance”.
>
> The VOTE is to Deprecate/Retire
+1 -- (rational) GitHub issues are easy
On Sun, Jan 26, 2020 at 9:03 PM Joshua Poore wrote:
>
> Hi Folks,
>
> I’m moving straight to a VOTE on this one.
>
> Some users have expressed trepidation on pushing issues/tickets through JIRA.
> Specifically, they find our labels, components, and issue
to it, its highly customizable,
> and a plugin culture is growing.
>
> At the end of the day, absolutely nothing is stopping anyone from shipping
> logs to another back-end. I did get a ticket the other day to support a DAL…
>
> Best,
>
> Josh
>
> > On Jan 25, 2020, a
On Sat, Jan 25, 2020 at 5:15 PM Joshua Poore wrote:
>
> Austin—good to hear from you.
>
> Apologies for the delay. Have been working with users last few days and
> wanted to give your email the appropriate attention—some good questions.
>
> Replies inline
>
> > On Ja
Hi Flagon,
Looking for info:
* I don't see much on analysing the data that gets collected. Very
interested in understanding the types of insights that people are
deriving. Pointers very welcome (esp. to specific use cases).
Apologies if missing something obvious...
* Additionally, is JIRA the
#2 looks super cool; still don't have a great sense of what project is
trying to do as to whether sufficiently in-line.
On Sat, Sep 28, 2019 at 9:38 PM Joshua C. Poore wrote:
> Hi Folks,
>
> I've been doing some sketches on Flagon logos. Probably we'll want a few
> for various things, but we
gt; On Sep 8, 2019, at 8:33 PM, Austin Bennett
> wrote:
> >
> > Looks super cool.
> >
> > I'm on the plane heading to ApacheCon -- anyone from the community around
> > Vegas this week?
>
>
Looks super cool.
I'm on the plane heading to ApacheCon -- anyone from the community around
Vegas this week?
55 matches
Mail list logo
