[Inpycon] Everybody Pays Policy

Thu Sep 26 10:18:11 CEST 2013

Hi,

On Thu, Sep 26, 2013 at 1:21 PM, Sreekanth S Rameshaiah <sree at mahiti.org>wrote:

> Hi,
> We are compiling the expenses and income. It will be made public. We are
> yet to receive few sponsorship fees and finish left out payouts (
> specifically to those who conducted the workshop).
>
> Awesome.

> There is no organisers vs community here. Every one is welcome to come
> together to create this event and make this a great experience.
>
> Great

> There is always a call for volunteers and every year some one stands up
> runs the event.
>
> We know that.

> Requesting all to focus on issues at hand and not translate every thread
> into a personal attack.
>
> Indeed. I would hope everyone here represents community not an individual
& not push/throw his personal opinion but whats is good for overall
community.

- sree
>
>
>
>
>
>
> On 26 September 2013 12:44, atul jha <koolhead17 at gmail.com> wrote:
>
>> Anand,
>>
>>
>> On Thu, Sep 26, 2013 at 12:40 PM, Anand B Pillai <
>> anandpillai at letterboxes.org> wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On Thursday 26 September 2013 12:18 PM, Noufal Ibrahim wrote:
>>> > atul jha <koolhead17 at gmail.com> writes:
>>> >
>>> >
>>> > [...]
>>> >
>>> >> Pycon is a community event not a event for profit.  Don`t
>>> >> blindly follow policies of other country things work differently
>>> >> here.
>>>
>>> I generally agree with this principle of not blindly following
>>> American policy here. I think I did mention it ealier when
>>> this discussion opened saying PSSI frames its own policies.
>>>
>>> We do need to frame local policies keeping in mind the Indian ethos.
>>>
>>> >
>>> > As somone who's been involved in organising this for a while, I'm
>>> > not "blindly" following anything. I genuinely think "everyone pays"
>>> > is a good idea regardless of who came up with it.
>>> >
>>> > Also, we're not looking to generate profit but an event does have
>>> > costs. We want to cover those in a way that allows us freedom to
>>> > conduct the event as we wish.
>>> >
>>> > To illustrate with an extreme case, if a sponsor said that they'd
>>> > pay us a crore for branding the conference with their name and
>>> > giving them the contact information of all the participation, we'd
>>> > be able to to give free entry to every delegate and do everything
>>> > in style but we'd say no.
>>> >
>>> > [...]
>>> >
>>> >> Its organizers responsibility to not select freeloaders.
>>>
>>> It is probably not a good idea to give free entry to volunteers.
>>> I kind of agree with the "Everybody pays" policy here.  Though
>>> I think volunteers should not pay the full price but should
>>> get some benefit of tiered pricing.
>>>
>>> I would rather suggest to reserve a certain section of early bird
>>> tickets for volunteers and co-ordinators instead. For example
>>> if the early bird ticket volume size is "N" it should be made
>>> rather N + V where V is the volunteer/co-ordinator population
>>> size. Keep this as a separate early bird category.
>>>
>>> We can identify volunteers using their email IDs early on
>>> and only allow those email addresses to book from this slot.
>>>
>>> This might be a way to avoid freeloaders.
>>>
>>> >
>>> > The devil is in the details.
>>> >
>>> > If you have concrete suggestions on how to identify and weed out
>>> > freeloaders without destroying the volunteer base, please post
>>> > them here. Or better yet, pick up the job of volunteer coordinator.
>>> > After all, advice is cheap.
>>> >
>>> >
>>> >>> How difficult is it to pay cheques to speakers in that case?
>>> >
>>> > Very very difficult. Like I said, the devil is in the details.
>>>
>>> A way to solve this would again be to ask speakers to pay up
>>> front and then refund the speakers who gave talks at the end of
>>> the conference. Again something not too easy with the details
>>> but possibly a way to identify speakers might be when they
>>> register - I think PyCon US does this - You can register
>>> as a regular attendee or a speaker.
>>>
>>> I think we need to tweak the "Everybody pays policy" to suit
>>> our local expectations.
>>>
>>> Is any takers for this?
>> I doubt.
>>
>>
>>>  >
>>> >
>>> > [...]
>>> >
>>> >
>>>
>>>
>>> - --
>>> Regards,
>>>
>>> - --Anand
>>>
>>> -
>>>
>>> --------------------------------------------------------------------------------------
>>> Software Architect/Consultant
>>> anandpillai at letterboxes.org
>>>
>>> Please note my updated email address <anandpillai at letterboxes.org>.
>>> Kindly update your address books.
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.11 (GNU/Linux)
>>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>>
>>> iQEcBAEBAgAGBQJSQ93+AAoJEMTxYeOp9eaosFQH/3PYdRKRj1hrUHCQUZXrLcpC
>>> 8n0NMEY3Btp5JTFJdA7565SB7a4v//AbMpivItxdQODj4Hp1+wVKddz/pmUK3OZw
>>> VhjkWHJFZ8wr7mEwej0559ZF18F7NbJTj0clz+ZeFXa3txvJyH5up88o5Rpa5SOo
>>> X8KUrHMJNS4oqsSJ8xspfV0bMJWBovR2V9ceobfjvYfnQChnsluxGuDRkywftZhr
>>> QrIxwz9l9EFTcScmHpw+noLqe3sFJkr4x0Au1tlk6V9tJElhwPf5SiO+uUoTuXj6
>>> lRh9vQnWZjMDSVbj0wABTT4Fh0s9+1vtRaN90yOEBVy6T98LVQFvzOeOHvabPQ4=
>>> =m6LP
>>> -----END PGP SIGNATURE-----
>>> _______________________________________________
>>> Inpycon mailing list
>>> Inpycon at python.org
>>> https://mail.python.org/mailman/listinfo/inpycon
>>>
>>
>>
>>
>> --
>> Atul
>>
>> www.atuljha.com
>>
>> irc(freenode) : koolhead17
>>
>>
>> _______________________________________________
>> Inpycon mailing list
>> Inpycon at python.org
>> https://mail.python.org/mailman/listinfo/inpycon
>>
>>
>
>
> --
> Sreekanth S Rameshaiah
> Executive Director
> Mahiti Infotech Pvt. Ltd.
> Bangalore, India - 560043
> Phone:  +91 80 4905 8444
> Mobile:  +91 98455 12611
> www.mahiti.org
> www.mahiti-infotech.com
>
> _______________________________________________
> Inpycon mailing list
> Inpycon at python.org
> https://mail.python.org/mailman/listinfo/inpycon
>
>

-- 
Atul

www.atuljha.com

irc(freenode) : koolhead17
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/inpycon/attachments/20130926/d85952a8/attachment-0001.html>