latest forum list draft.. I support all other efforts but I do think this is really useful list to keep updated:

Code: [Select]

ACTIVE
1.6.17 - bhuz - Bhuz
1.6.12 - bitcube - cube
1.6.25 - bue - twitter
1.6.21 - cyrano - pc
1.6.49 - datasecuritynode - DataSecurityNode
1.6.14 - dele-puppy - puppies
1.6.28 - delegate-1.lafona - lafona
1.6.27 - delegate-clayop - clayop
1.6.40 - delegate.btsnow - dannotestein(?)
1.6.26 - delegate.ihashfury - iHashFury
1.6.42 - delegated-proof-of-steak - ?
1.6.20 - elmato - ElMato
1.6.16 - fox - Fox
1.6.23 - harvey-xts - Harvey
1.6.32 - holytransaction - darbon
1.6.35 - in.abit - abit
1.6.43 - maqifrnswa - maqifrnswa
1.6.19 - mindphlux.witness - mindphlux
1.6.24 - mr.agsexplorer - boombastic
1.6.45 - rnglab - rnglab
1.6.13 - roadscape - roadscape
1.6.15 - spartako - spartako
1.6.30 - spectral - Spectral
1.6.29 - triox-delegate - triox
1.6.34 - verbaltech2 - Thom
1.6.18 - wackou - wackou
1.6.22 - xeldal - Xeldal
edit: updated list.
init* delegates are omitted. only one unnamed witness remains.
i made one assumption: delegate.btsnow belongs to dannotestein.

Quote from: bytemaster on October 15, 2015, 09:43:46 pm

I think we should create a private slack group for witnesses to coordinate in, especially over sensitive issues like potential hard forking security fixes.

I have created a slack group 'Bitshares Witnesses' in slack and will be inviting the witnesses.

Quote from: clayop on October 15, 2015, 09:06:32 pm

I think I'd rather have two VPS (2 Core 8G ram) with failover script than one higher-end VPS (4 Core 15G ram). Can you advice me?

I'm not sure which would be better.  They both have advantages and drawbacks.   I will help you out either way if you want to use the script.  I just want to be clear it is in its very early stages.  For example the reset if production falls below 50% has never been tested.  I am pretty sure it will work, but I would hate for you to rely on it and be let down.

I'll start with some better documentation in the script thread

Thanks betax and rng.  Be careful.  I forgot to mention the first thing it will do is kill any running witness_node on your box so that it can start a new one in a screen called witness.  I would not suggest running it on your main production witness until it has been much more thoroughly tested.

Quote from: rnglab on October 08, 2015, 06:25:53 am

Quote from: bitsacer on October 07, 2015, 11:01:40 am

I could help for turkish translation. Can someone send me the link here please. I was just thinking about the effectiveness of short videos like the ones Salman Khan does on Khan Academy. Many people will have hard time comprehending totally what such things like a witness or a delegate are and what they do . Short videos  each couple of minutes would really help people  understand basic terminology and the functions .

@bitsacer, are you dairemerkezi on Transifex? If so you are doing it great job translating graphene-ui into Turkish, we should grant  Reviewer permissions.

Same to inarizushi Transifex user wtth French translation. If you read this please let me know so we can keep in touch.

Remember that changes on translation source file are pulled once a day from github.com/graphene-ui.
You can click on Watch Project from the source file page of the project to get notified each time new strings comes from github (https://www.transifex.com/bitshares/graphene-ui/content/)

When translations get completed and reviewed I'll be pushing them to github. Reviewers and Language Coordinators can do that themselves if they want.

I'm glad to see more people joining

Hi , could you briefly describe to me how to push translation from transifex to github . Thanks