Re: Please merge the three pull requests on GitHub

[Andrew Miloradovsky <miloradovsky gmail com>]

Thanks for the reply!

On 04/19/2017 01:17 PM, Alexánder Alzate Olaya via planner-dev-list wrote:
> Well, it seems like you are not having into account that the GNOME
> Github mirror is not maintained by any planner developer. Actually, and
> I'm not sure here, I think it is automatically "maintained".
I admit I may have misused the GitHub mirror(s). But wasn't aware of
that until the PR was closed.
Honestly, I thought the GH mirrors were an auxiliary feedback channels,
equally valuable.
> As anywhere, there are rules in GNOME projects, and for most GNOME
> contributors there is a basic rule: "Patches solve issues" and the
> issue tracker is bugzilla.gnome.org, so, how do you pretend to solve an
> issue which is not being tracked? how do you track those changes?
>
> Contributing in your case is pretty straightforward:
>
> 1 - Create a [GNOME Bugzilla](https://bugzilla.gnome.org/) account.
> 2 - Checkout if the issue you are referencing is already being tracked.
> 3 - File a bug if there is not such issue.
> 4 - Attach any patch you considere solves the issue.
Ok, I've just created an account on the Bugzilla, will try to comply,
still learning; but attaching patches to the "bugs" (issues) seems
like... a little bit more hassle than absolutely required.
> I'm just a developer and not a Planner maintainer and I think I do
> understand you problem here, but take a while to realize that Github is
> used by GNOME to mirror projects, not to maintain those projects.
>
> On Wed, 2017-04-19 at 10:25 +0000, Andrew Miloradovsky wrote:
> > Maybe I should give the explicit link to the branch with the fix I
> > mentioned:
> >
> > https://github.com/amiloradovsky/planner/tree/zero-width-lines
> >
> >
> > On 04/19/2017 09:46 AM, Andrew Miloradovsky wrote:
> > > Hello, Planner developers!
> > >
> > > Several months ago I had a not very pleasant experience
> > > in an attempt to contribute to GNOME, namely Planner:
> > > I wanted to commit a fix for a strange issue which happened to me
> > > on a
> > > distribution.
> > > It was somewhat hard to reproduce but the patch was, IMO, very
> > > reasonable nevertheless.
> > > I was told by the port maintainers to better commit the fix
> > > upstream. --
> > > Of course!
> > >
> > > I noticed that many GNOME projects have a mirror on GitHub,
> > > and tried to open a pull request, in hope it will be merged, sooner
> > > or
> > > later.
> > > Alas, that PR was automatically closed and I was sent into the
> > > documentation,
> > > which basically told me to go fuck myself...
> > >
> > > Recently I checked how much Planner progressed during these months,
> > > and what happened to the "open-closed" PR's on GitHub, by the
> > > way...
> > > I understand that GitHub is a questionable enterprise --
> > > convenient,
> > > but hosting FOSS projects there is not very wise in the long run.
> > > OTOH, by the nature of Git, it shouldn't matter where the submitted
> > > patches are hosted,
> > > even if that's hell.
> > >
> > > All that being said: for God's sake, somebody,
> > > just forget all those ideological considerations for a moment,
> > > merge the PR's, or at least leave a comment why you wouldn't!
> > > Showing some activity on GH by not ignoring those "open-closed" PR,
> > > I'm sure, may spark the interest for further contributions! Next
> > > time,
> > > I promise to use Bugzilla or whatever in-house GNOME tools I'm
> > > supposed
> > > to use.
> > >
> > > https://github.com/GNOME/planner/pulls?q=is%3Apr+is%3Aclosed
> > _______________________________________________
> > planner-dev-list mailing list
> > planner-dev-list gnome org
> > https://mail.gnome.org/mailman/listinfo/planner-dev-list
> _______________________________________________
> planner-dev-list mailing list
> planner-dev-list gnome org
> https://mail.gnome.org/mailman/listinfo/planner-dev-list