David Pelaez davidpelaez

Hello. You are great and I don't want to use an external issue tracker without the quality UI that you guys provide. I'm allergic to bad design and I love you for being my medicine. I'm building an app with UI as well and my client needs to report issues with screenshots most of the time to present what he perceives as the problem. There is no way to attach files on issues at the moment and that is making Github Issues useless for things that include UI on web, mobile and desktop!

I googled and found this extremely complicated thing: http://feeding.cloud.geek.nz/2012/06/attaching-files-to-github-issues.html and I wanted to let you see it and hopefully you will get worried about what people do in order to complete a task that isn't weird. I understand your well funded obsession to keep a clean core of features, but I think this is something you should honestly fix.

Please don't make me use anything else. As a coder I know putting attachments is pretty simple. You can list them like in emails, they don't eve

	1. "Experts" are clueless.
	2. Customers cannot tell you what they want.
	3. Biggest challenges beget the best work.
	4. Design counts.
	5. Big grahics. Big font.
	6. Jump curves, not better sameness.
	7. "Work" or "doesn't work" is all that matters.
	8. "Value" is different from "price".
	9. A players hire A players.
	10. Reals CEOs DEMO

	Hi Reyndert,

	we are testing the routes and some improvements and bug fixes we made. There are points missing, but the biggest parts are covered. We are starting a code refactoring process, that means cleaning the code to make it better and begin to prepare the applicant and recruiter apps to a more finished production state code that can be reviewed. We are also doing that in the back-end to begin to prepare the app for sysadmin. You'll get some updates on detail from Francisco in a little bit, but we have agreed that it's time to shift into this phase to approach code reviewal. I guess this is very good news to complement the other updates from Francisco. The weekend is busy for both on work and personal important dates with friends, so we will be slightly offline until monday. Not totally distant, but slightly offline. So if you have important issues to fix let us know by email, and we'll back on monday figuring out how to proceed in this final phase.

	Best,


	David Peláez Tamayo
	Designer & Entrepreneur

	[David@Davids-MacBook cvive]$ git pull origin master
	remote: Counting objects: 123, done.
	remote: Compressing objects: 100% (29/29), done.
	remote: Total 73 (delta 54), reused 62 (delta 43)
	Unpacking objects: 100% (73/73), done.
	From https://github.com/cvive/cvive
	* branch master -> FETCH_HEAD
	Updating f381129..e483ed9
	Fast-forward
	app/assets/.DS_Store \| Bin 6148 -> 6148 bytes

	Caso1:
	Un dashboard para un admin dashboard. Hay mucha mucha información viniendo del servidor y diferentes visualizaciones de esa información, cada una es casi como un componente independiente. Mucho "composite" y alertas que aparecen como growl y luego entran a modelos de datos que se ven como tablas o como charts pero usan el mismo dataset. Se puede pensar algo así como un dataset, muchas visualizaciones. Es más pasiva la observación porque el comportamiento explica al usuario todo lo q tiene q saber, es un dashboard para monitoreo.

	Caso2:
	Una aplicación mucho más interactiva para usuarios que están componiendo playlists y creando textos que son acompañados por la música. Hay mucho más input del usuario y aunque hay componentes todo esta altamente inter-relacionado, think iMovie o Premiere.

	IP Address 200.X.X.X
	VPN Device Description ASA CISCO 5520
	VPN Device Version 8 04
	Encryption Domain 172.X.X.X
	Tunnel Properties VPN Device
	Protocolo IPSEC
	Modo de Conexión SITE TO SITE
	Horario de Acceso 24/365
	Authentication Method SHA
	Encryption Scheme 3DES

	config setup
	protostack=netkey


	conn vlipco_credibanco
	ikev2=no
	authby=secret
	auto=start
	keyingtries=1
	type=tunnel

	version 2.0


	config setup
	plutodebug=all
	protostack=netkey
	nat_traversal=yes
	oe=off

	conn vc

	# Kernel sysctl configuration file for Red Hat Linux
	#
	# For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
	# sysctl.conf(5) for more details.

	# Controls IP packet forwarding
	net.ipv4.ip_forward = 0

	# Controls source route verification
	net.ipv4.conf.default.rp_filter = 1

	davidpelaez: https://gist.github.com/davidpelaez/4719163
	[7:36pm] LetoTo: thats wrong
	[7:36pm] LetoTo: net.ipv4.ip_forward = 1
	[7:36pm] LetoTo: net.ipv4.conf.default.rp_filter = 0
	[7:37pm] LetoTo: also add
	[7:37pm] LetoTo: net.ipv4.conf.all.send_redirects = 0
	[7:37pm] LetoTo: net.ipv4.conf.default.send_redirects = 0
	[7:37pm] LetoTo: then run sysctl -p
	[7:37pm] davidpelaez: ok
	[7:37pm] davidpelaez: one sec