WordPress.org

Making WordPress.org

Opened 5 years ago

Last modified 3 months ago

#221 assigned task

Open-Source WordCamp.org

Reported by: iandunn Owned by: iandunn
Milestone: Priority: normal
Component: WordCamp Site & Plugins Keywords:
Cc:

Description

We should move as many components of WordCamp.org as possible into the Meta repo, so that it's open to the community to contribute.

Before each piece can be moved, it will need to be audited for any security vulnerabilities or sensitive information.

Change History (14)

#1 @iandunn
5 years ago

  • Owner set to iandunn
  • Status changed from new to assigned

#2 @iandunn
5 years ago

In 115:

WordCamp Calendar: Move from private WordCamp repo. See #221.

#3 @iandunn
5 years ago

In 116:

WordCamp Canonical Years: Move from private WordCamp repo. See #221.

#4 @iandunn
5 years ago

In 117:

WordCamp Fonts: Move from private WordCamp repo. See #221.

#5 @markoheijnen
5 years ago

  • Cc info@… added

#6 @iandunn
4 years ago

In 171:

WCPT: Move from private repository. See #221.

#7 @jeffr0
4 years ago

  • Cc jeffc@… added

#8 @iandunn
4 years ago

We should also open-source the mu-plugins so things like #502 can be contributed to by the community.

Subversion only supports svn:external'ing files from within the same repo, so I'll migrate the few that need to remain private to a new mu-plugins-private directory and then move the public ones to meta.

#9 @obenland
4 months ago

@iandunn Do you know what's left to do on this ticket? How far away is this from being closable?

#10 @iandunn
4 months ago

Almost everything is done. The two things left are the camptix-extras and wordcamp-shortcodes plugins. Most of camptix-extras has already been opened, and a few of the remaining parts will need to stay closed.

Neither are a high priority, since they're not important or commonly used features. I'm trying to focus my time on the things that will make the biggest impact, so I imagine it'll be a long time before I'm able to close this out.

#11 @obenland
4 months ago

How much time do you think it'll take to complete this?

If I learned anything over the last two weeks, it's that finishing things and crossing them off sometimes take a surprisingly short time but it gives you a great sense of accomplishment and peace of mind.

#12 @iandunn
4 months ago

If things go smoothly, I'd guess that it'd take roughly 2 hours to clean up formatting, review the code for potential security issues and private data, test any changes, migrate it, deploy it, and re-test on production.

That'd have a very small impact though, and time is very limited. Saying "yes" to this means saying "no" to other things. Since there are so many things that will make a bigger impact, to me it feels like time spent here would essentially be wasted in comparison.

Even if this ticket is closed, there'll always be hundreds of other open ones that we don't have time to get to. I think that's just the nature of a large open source project (and, to some extent, any software project, or any project of any type). I think prioritizing the things that will make the biggest impact, and then focusing on those few things, is the best way to serve the project.

#13 @iandunn
3 months ago

In 6714:

CampTix Tweaks: Open source functions from camptix-extras.

With this, there's nothing left in camptix-extras, so it's being removed.

See #221

#14 @iandunn
3 months ago

In 6730:

WordCamp Miscellaneous: Open source the map of active groups.

See #221

Note: See TracTickets for help on using tickets.