Improvements to aid in community contributions and adoption about opentrace-cloud-functions HOT 4 OPEN

Thanks @qtangs; I do appreciate the detailed work that the TraceTogether team has done, especially those related to overcoming the issues with Bluetooth.

In the mean time, are community contributions being accepted? And are community maintainers welcomed?

Some PRs are already opened across the different repos. It'd be great if we can quickly merge them and not let them go stale so as to leverage the initial wave of community interest around the project.

I do believe that OpenTrace can be incredibly useful, and we should allow the community to contribute and adopt with little friction.

I look forward to helping improve OpenTrace along with the rest of the open source community.

from opentrace-cloud-functions.

Hi, is there a plan to provide a reference implementation of processUploadedData.ts as well? Its a bit hard to follow how the keys are matched without it.
const processUploadedData = async (object: ObjectMetadata) => {
throw new functions.https.HttpsError('unimplemented', 'Not implemented yet');
};

from opentrace-cloud-functions.

Thanks @achrinza for the detailed suggestions. We appreciate all the points. Our team is in the process of working out these areas along with many other priorities. We will provide update when possible. Stay tuned.

from opentrace-cloud-functions.

Hi @qtangs; Some PRs have been opened up in this repo to resolve some of the issues raised in this issue.

from opentrace-cloud-functions.