Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Responsibilities of PyCon APAC community #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Responsibilities of PyCon APAC community #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions guideline/cfh.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ help run PyCon Asia Pacific in 2017 in a location they are local to. PyCon APAC
Asia-Pacific countries to come together to meet with fellow Python users. The
same can be said for anyone adopting an exploratory perspective towards Python.

The above text proposes that a certain group 'owns' PyCon APAC. The below text also puts forth certain rules and requirements which would-be organizers needs to adhere to before they can be _considered_ as eligable to organize PyCon APAC. If we endorse a certain party, I think we also need to be clear on the responsibility that we hold as the party that endorses a certain organizer. We cannot just say "yes, you can hold PyCon APAC" but do not follow through on issues that might occur after that.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better break this to multiple lines. It'll make commenting easier.

This paragraph doesn't look like part of the document, but your comment for the document, @iq8al ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, those are my comments, which should be overwritten with the real text if we can come to a conclusion @yungyuc

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer to put comments and discussions in github issue/PR tracker. In this way the document itself remains self-contained.

If we really want to put our comments into the document, we should explicitly mark it. Because I don't like this idea, I am not proposing a format. But I think such a format should include a clear todo mark (XXX, FIXME, etc.) and a the commenter's identity.

@iq8al could you go with either way (or another option you like) in your next update of this PR?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, the issue tracker is there to be used anyway, so comments will go there instead. Proposal to editing the document can go as PR then.


## Timeline for Proposals

The Call for Participation will run until the following deadline for
Expand Down Expand Up @@ -83,8 +85,7 @@ These are the requirements that an on-site team will sign-up to when submitting
a proposal. Changes to these requirements are possible, but they must be signed
off by the PAC before they can be put in place.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think being or being affiliated with a legal entity is important. This slightly raises the bar of holding PyCon APAC, but it looks a reasonable constraint to me. It's not an overly difficult criteria, but it provides a clear signal that anyone who wants to hold PyCon APAC should establish a sound user base in the hosting country.

Also most if not all of the local PyCons started small and grew, I guess we all started with a certain kind of legal entity. Be it a commercial company or a NPO. Otherwise it's difficult to deal with authorities or sign contracts. The representing entity doesn't need to be totally for Python or PyCon. PyCon Taiwan works with a company and a NPO established by and for a lot of Taiwan FOSS activists, and we plan to continue this setting until we see clear benefits to make a Python-specific organization.


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The choice of the words "part of" instead of "members of" leaves enough room for the relation between the organizing team and the representing entity.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I see your point @yungyuc . That makes sense. So the organizers don't have to have a legal entity of their own, but some sort of legal entity which can back them.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes @iq8al that's my understanding, and it sounds reasonable to me.

1. The conference will be financially and legally run by an entity registered
at the hosting country and for which the on-site team is part of.
1. The conference will be financially and legally run in the hosting country and for which the on-site team is part of.

2. The on-site team must be geographically located in a country in the Asia
Pacific and Australasia region.
Expand Down