Re: [asciidoc-wg] 2021 Program plan and budget

[Dan Allen <dan@xxxxxxxxxxxxxx>]

Thanks Paul! That's exactly the information I was looking for.

Since the fees are informed by the budget, I don't think this step was skipped so much as it is now the current step ;) So let's tackle it.

I find the justification you gave for the fees to be sound. In the spirit of both fairness and practicality, it's good to start with a basis that has worked for other groups. And it meets the requirement stated by several committee members to keep the fees at or below the 10K mark.

We should be cautious about stating to early that the fees are fixed year over year once set. Since we're operating on a hairpin budget in 2021, it's reasonable to say the fees aren't going to go down. But if the committee decides on a more ambitious plan after the first year (for example, to make room to develop the compliance program), it may be necessary to increase the fees to cover those goals. So I think we just need to leave room for that to happen.

I have a few follow-up questions that will help us complete the current step:

Who is expected to make the update to the charter? Is that the responsibility of the Steering Committee chair?

Who will put a screenshot of the budget into the program plan document?

What exactly do we need to vote on in the first vote? Are we voting on the fee schedule, or are we voting to ratify the draft charter with the fees added to it? (I just need to understand where the charter vote fits in).

Unless one of the committee members has an objection, or an objection is otherwise raised, I think we're ready to move forward with a vote.

Best Regards,

-Dan

On Wed, Dec 9, 2020 at 10:29 AM Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi Dan.

I’m glad you asked the question, as I suspect others have the same question.  

We have been discussing the program plan and potential budget to achieve the basics of what’s in the program plan.  i.e., the documents you distributed capture the proposed costs we need to cover in order to execute through 2021.

The step that “got skipped” is that we need to formally establish the fees that each member organization pays.  This is actually an update to the charter, and is a formal requirement of the Steering Committee to do so.  

By the way, for everyone’s benefit, once these fees are established, it’s expected that the fees will remain in place year-over-year.  That is, while it is possible, we don’t typically see working groups revise their fees annually.  This is to allow for more predictable budgeting for all our members.  

Based on the discussion at the last meeting, and the fact that we are looking at an expense target of roughly $43,000, we are recommending the following fee table:

Annual Corporate Revenues greater than $1 billion	$10,000
Annual Corporate Revenues greater than $100 million but less than or equal to $1 billion	$8,000
Annual Corporate Revenues greater than $10 million but less than or equal to $100 million	$6,000
Annual Corporate Revenues less than or equal to $10 million	$4,000
Annual Corporate Revenues less than $1 million and < 10 employees	$1,500

A few comments regarding this proposed fee table:

• the “revenue bands” match those in other working groups, and is consistent with our membership fee structure to enable organizations of all sizes to participate and to contribute fees proportionately
• using these bands, we will almost exactly cover the expenses that are identified in the draft budget that was distributed
• we believe these are consistent with the discussions that have been had to date

So, to your suggestion of moving to a vote - that’s fine, unless any other members feel there is a need for additional discussion. If we are moving direct to a vote, then we will put together two draft resolutions for the Steering Committee members to electronically vote on: 

1. Approve the fee schedule (once approved, these fees will remain in place until changed again by the Steering Committee)
2. Approve the 2021 Program Plan and the 2021 Budget (we will approve these annually)

Hope this helps. 

Thanks ... Paul

On Tue, Dec 8, 2020 at 3:29 PM Dan Allen <dan@xxxxxxxxxxxxxx> wrote:

Paul,

I don't feel another meeting is needed. I think we should be asking whether it's time to move forward with a vote. If not, I'd like to know what the Steeering Committee members need in order to get to that point.

> The Steering Committee also needs to set the fees for 2021 that will go into the charter.

Wait, I thought the fees were determined by the budget. Or when you say "set" are you implying a ratification of that computed value?

Best Regards,

-Dan

On Mon, Dec 7, 2020 at 3:05 PM Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx> wrote:

Do we need a Steering Committee meeting to discuss and vote on the 2021 Program Plan and Budget? The Steering Committee also needs to set the fees for 2021 that will go into the charter.

Thanks ... Paul

Paul Buck

VP, Community Development  |  Eclipse Foundation  |  +1.613.220.6507 (m)

On Sat, Dec 5, 2020 at 4:57 PM Dan Allen <dan@xxxxxxxxxxxxxx> wrote:

This is not the appropriate thread to discuss domain names. The focus of this thread should be on the program plan and budget. Getting that wrapped up is vital to the success of this endeavor. It does not involve selecting or registering any domain names.

Deciding on domain names will be a task for 2021. When that time comes, we will have a proper thread to discuss the options. We can go through all the pros, cons, and confusions and make a decision that best serves our mission.

I will leave it at this. I suggested asciidoc-lang.org becaue that's a very common naming convention for a language project site. I can cite examples when it comes time to discuss it. For now, that mention in the program plan is only meant as a way to identify the project site unique from other sites.

Please stay focused on the program plan and budget and let's not get sidetracked.

Thank You and Best Regards,

-Dan

--

Dan Allen, Vice President | OpenDevise Inc.

Pronouns: he, him, his

Content ∙ Strategy ∙ Community
opendevise.com

_______________________________________________
asciidoc-wg mailing list
asciidoc-wg@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/asciidoc-wg

_______________________________________________
asciidoc-wg mailing list
asciidoc-wg@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/asciidoc-wg

--

Dan Allen, Vice President | OpenDevise Inc.

Pronouns: he, him, his

Content ∙ Strategy ∙ Community
opendevise.com

_______________________________________________
asciidoc-wg mailing list
asciidoc-wg@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/asciidoc-wg

_______________________________________________
asciidoc-wg mailing list
asciidoc-wg@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/asciidoc-wg

--

Dan Allen, Vice President | OpenDevise Inc.

Pronouns: he, him, his

Content ∙ Strategy ∙ Community
opendevise.com