wxFormBuilder on GitHub

[Jan Niklas Hasse]

Hi!

I know that wxFormBuilder is not maintained by the wxWidgets developers, but I've recently brought it on the wxFormBuilder mailing list, that a move to GitHub might be good for the project. For that I think it would be great if it was a repository under the wxWidgets organization.

Would you accept that or do you think wxFormBuilder should create its own organization instead?

Best regards
Jan Niklas

[Bryan Petty]

On Thu, Sep 1, 2016 at 7:57 AM, Jan Niklas Hasse <jha...@gmail.com> wrote:
> Would you accept that or do you think wxFormBuilder should create its own
> organization instead?

It's a great tool, and I'm sure most people like the idea of the
organization helping host/shepard smaller wxWidgets-focused projects
when they need the help, and generally, I feel this type of
"sponsorship" is ideal for new language bindings for example. I always
felt like more bindings should have worked harder to be part of the
official project.

Although, the official organization has tried to keep away from
appearing to "favor" any one specific GUI form editor tools in
particular (even though wxFB is arguably the best free, and open
source tool). It's also a little harder to recommend stewardship of
sub-projects that don't quite fit under the wxWindows license (i.e.
wxFormBuilder is GPLv2, which totally make sense, it shouldn't be
under a license designed for a library).

In my opinion, it should use it's own GitHub organization for
development, but maybe others feel different. Definitely worth the
discussion, thanks for bringing it up here.

--
Regards,
Bryan Petty

[Vadim Zeitlin]

On Thu, 1 Sep 2016 06:57:59 -0700 (PDT) Jan Niklas Hasse wrote:

JNH> I know that wxFormBuilder is not maintained by the wxWidgets developers,
JNH> but I've recently brought it on the wxFormBuilder mailing list, that a move
JNH> to GitHub might be good for the project. For that I think it would be great
JNH> if it was a repository under the wxWidgets organization.

What exactly does this entail? I understand that it implies some sort of
recognition of wxFormBuilder as wxWidgets project, which is somewhat
questionable -- not because I have anything at all against wxFormBuilder,
quite the contrary, but because there are several other projects in the
same area and it's not clear why should we single just this one, so we need
to either extend the invitation to all the other ones too, or not do it at
all. But beyond this, does this have any technical repercussions? E.g. do
you know whether this means that we'd have the same admins/developers/
permissions/whatever for all projects or do they remain completely
independent other than belonging to the same organization?

Thanks,
VZ

[Tobias T]

Seems like there is an offical github repo now (Since 1. September) at:
https://github.com/wxFormBuilder/wxFormBuilder

Regards,
Tobias

[Patrick Geltinger]

Like Tobias said, we have created our own organization, wxFormBuilder,
for now.

It's understandable, that wxFormBuilder should not pose an exception
when it comes to being included in the wxWidgets organization.
Maybe we can talk about the inclusion again, sometime in the future.

To answer your question concerning the technical consequences:
GitHub organization members can/must be organized in teams.
The organization itself only has Admin/Member permission levels, but
teams can be given Admin/Write/Read permissions on a per-repository
basis, just like personal repositories.

[Vadim Zeitlin]

On Fri, 9 Sep 2016 09:24:15 +0200 Patrick Geltinger wrote:

PG> It's understandable, that wxFormBuilder should not pose an exception
PG> when it comes to being included in the wxWidgets organization.
PG> Maybe we can talk about the inclusion again, sometime in the future.

Yes, certainly. I'm not really opposed to this, but I do think we should
ask authors of other, especially open source, similar projects if they'd
like to be hosted under wxWidgets organization umbrella and spending time
on this is just not something I'd prefer to be doing right now, sorry.

PG> To answer your question concerning the technical consequences:
PG> GitHub organization members can/must be organized in teams.
PG> The organization itself only has Admin/Member permission levels, but
PG> teams can be given Admin/Write/Read permissions on a per-repository
PG> basis, just like personal repositories.

So there are no technical obstacles to doing this, thanks for clearing
this up!

VZ