BitShares Forum

Main => General Discussion => Topic started by: Pheonike on November 03, 2014, 05:52:56 pm

Title: Delegate Classifications
Post by: Pheonike on November 03, 2014, 05:52:56 pm

I know its been discuss to death, but i do think we need to define categories for types of delegates. Since on a technical level there is nothing to distinguish what delegates do. There should be some type of classification so at glance we know what their role is. Just like a company has different departments that focus on different aspects of the business. Here are some I thoughts of below

Marketing Delegate - promotes and expand user base. Works on branding with online/offline campaigns
Developer Delegate - Works on adding new functionality/Dapps to Bitshares
Technical Delegate - Standard delegate. Signs blocks. Help test new features/functions in client. Quality control.
Communications Delegate - Coordinates projects between delegates. Moderates communications within Bitshares (what Fuzz does ;) )

Again there are no required code changes. Just a way to make since on what everyone is contributing if they are a delegate.

Title: Re: Delegate Classifications
Post by: xeroc on November 03, 2014, 05:55:57 pm
So you would suggest to name the delegates accordingly?

tech.delegate.xeroc
support.delegate.xeroc
marketing.delegate.xeroc
development.delegate.xeroc
?

I like that idea ... however, if you want to do a subset of all of them?

I'd say we make the delegate publish a page/document that describes purpose/goals/finance (however that page might be easy to *change* afterwards
Title: Re: Delegate Classifications
Post by: Pheonike on November 03, 2014, 05:59:11 pm

It does not have to be reflected in their name. But when we get some kind of delegates site, it would be useful to know what your delegates stands for.
Title: Re: Delegate Classifications
Post by: xeroc on November 03, 2014, 06:10:46 pm
Ah.. ok ..
AFAIK cass ia working on sth like this ...
Title: Re: Delegate Classifications
Post by: kisa on November 03, 2014, 06:20:03 pm
So you would suggest to name the delegates accordingly?

25% tech.delegate.xeroc
40% support.delegate.xeroc
20% marketing.delegate.xeroc
15% development.delegate.xeroc
?

I like that idea ... however, if you want to do a subset of all of them?

I'd say we make the delegate publish a page/document that describes purpose/goals/finance (however that page might be easy to *change* afterwards