OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio

IPB

Welcome Guest ( Log In | Register )

Profile
Personal Photo
Options
Options
Personal Statement
kucir doesn't have a personal statement currently.
Personal Info
kucir
Age Unknown
Gender Not Set
Location Unknown
Birthday Unknown
Interests
No Information
Statistics
Joined: 11-January 18
Profile Views: 631*
Last Seen: 23rd June 2019 - 04:12 AM
Local Time: Oct 14 2019, 09:17 PM
8 posts (0 per day)
Contact Information
AIM No Information
Yahoo No Information
ICQ No Information
MSN No Information
* Profile views updated each hour

kucir

Members


Topics
Posts
Comments
Friends
My Content
19 Oct 2018
takže jsme se s Pavlem a Alexandrem dohodli na sraze a abysme předešli sáhlým debatám o čase, tak jsme ho stanovili.
sraz bude ve čtvrtek 1.11. v Praze Dejvicích, v kavárně v Národní Technické Knihovně

Pokud chcete a nemůžete v daném čase, pište to sem taky.
13 Mar 2018
My fellow Geminions,
In short, I talked to Robin from Planet and he stated, that he is overloaded with all communication and it will help him if community can create some fault tracking system.
So I am stepping in to offer coordination of this activity.

My plan is to have ready solution in max 2 weeks. I believe, that we can make it in 1 week.
Lets use one day for gathering all possibilities and then we will see who will participate and which direction we will go.

Philosophy:
It must be as simple as possible. There is no need for some complicated system.
It must help. Save energy and time. Not another system for system.
As it will help Planet, it can also help us as we will have info about which issues are happening.

I see two possibilities:
1) we will write something. (simple database and web interface can do)
2) we will use some software which already exist.

Required features:
- learning time max 30 minutes.
- we must be able to modify which fields will be in problem record.
- system itself or admins must be able to categorize or merge reoccurring problems

how problem record will look like?
- short name of problem
- hardware / software
- priority (cannot use device / can live with it / just a visual problem...)
- description of problem
- problem category

- name of backer/owner
- indiegogo order id
- email
- date and time

- place for additional notes
- log of all operations with problem record

additional features:
- email notification in case of changes with record
- export to some excel sheet
- chance to add photo/video
- standard user can create and later edit his problem record
- community admins can organize records, request missing info from affected users, respond to users in case that some solution/workaround will be discovered, close records which were already explained (e.g. compass not working)
- Planet crew can view records, add notes, make some kind of statistic.

All ideas and help is welcome. I am just trying to speed it up by defining everything from beginning.

What about name of our system? Observatory?
27 Feb 2018
takže vítám všechny CZ/SK (budoucí) majitele gemini. Myslím, že naším největším úkolem bude společný boj s mizernou konfigurací české klávesnice. Pojďme začít tím, že se dáme do kupy.

Já jsem Tomáš, sídlím v Praze. Spoluprovozuju kavárnu, dělal jsem roky v IT a studoval jsem psychologii.
mé kořeny: Psion revo, Psion 5mx, HTC universal, HTC Athena X7500 a pak smutné neproduktivní období androidích telefonů (s bluetooth klávesnicí, s drátovou klávesnicí nebo alespoň přes shareKM sdílenou klávesnicí a myší z notebooku.)
Last Visitors


24 Jul 2018 - 9:50


24 Feb 2018 - 3:58


23 Feb 2018 - 8:31


22 Feb 2018 - 7:16

Comments
Other users have left no comments for kucir.

Friends
There are no friends to display.
RSS Lo-Fi Version Time is now: 14th October 2019 - 11:17 AM